Troubleshooting Guide

Common issues and how to resolve them.

Redirects Not Working

1. Check Deployment Status

Ensure your redirects have been deployed to Cloudflare. Go to your website dashboard and check the deployment status indicator. If it shows "Pending", click "Deploy" to push your changes.

2. Verify Worker Route

The Cloudflare Worker must be configured for your domain. Check that the worker route matches your domain pattern (e.g., *.yourdomain.com/*).

3. Clear Cache

Browsers and CDNs may cache old responses. Try:

• Hard refresh: Ctrl+Shift+R (Windows) or Cmd+Shift+R (Mac)
• Clear browser cache
• Purge Cloudflare cache from the dashboard

4. Check Source URL Format

Ensure your source URL matches exactly. Common issues:

• Trailing slashes: /page vs /page/
• Case sensitivity: URLs are case-sensitive by default
• Query parameters: Source URL should not include query strings

Deployment Failures

Invalid API Token

If deployment fails with an authentication error:

1. Go to Settings → Cloudflare Integration
2. Regenerate your API token in Cloudflare
3. Update the token in RedirectFlow
4. Ensure the token has "Workers Scripts:Edit" permission

Worker Size Limit

Cloudflare Workers have a 1MB size limit. If you have thousands of redirects, consider:

• Using pattern-based redirects instead of individual rules
• Splitting redirects across multiple websites
• Upgrading to a plan with KV storage for large redirect sets

Zone Not Found

This error means the domain isn't in your Cloudflare account. Verify:

• The domain is added to Cloudflare
• Your API token has access to that zone
• The domain name is spelled correctly

Redirect Loops

If you're seeing "ERR_TOO_MANY_REDIRECTS" in the browser:

Check for Circular References

Use the RedirectFlow validator to detect loops. Go to your website dashboard and click "Validate Redirects".

Check Origin Server

Your origin server might have its own redirects that conflict with RedirectFlow. Common causes:

• WordPress plugins with redirect rules
• .htaccess redirect rules
• SSL/HTTPS forcing redirects

HTTPS Redirect Conflicts

If Cloudflare's "Always Use HTTPS" is enabled along with a HTTP→HTTPS redirect in RedirectFlow, you may get a loop. Use one method, not both.

Slow Redirects

Redirects should complete in under 10ms. If you're experiencing slow redirects:

• Check redirect chains: Each hop adds latency. Flatten chains to direct redirects.
• Reduce regex complexity: Complex regex patterns take longer to evaluate.
• Use specific matches: Exact path matches are faster than wildcard patterns.
• Check Worker location: Ensure Cloudflare Workers are enabled for nearby edge locations.

Import Errors

CSV Format Issues

Ensure your CSV follows the correct format:

source,destination,status_code
/old-page,/new-page,301
/another-old,/another-new,302

Character Encoding

Save your CSV as UTF-8. Special characters in URLs should be URL-encoded.

Duplicate Sources

Each source URL must be unique within a website. The import will skip duplicates.

Debug Mode

Enable debug mode to see detailed information about redirect processing:

Add ?_rf_debug=1 to any URL to see:
- Matched redirect rule
- Processing time
- Cache status
- Worker version

Example: https://yourdomain.com/old-page?_rf_debug=1

Note: Debug mode only works when accessed from IP addresses in your allowed list.

Still stuck? Contact our support team at support or check our status page for any ongoing issues.

← SEO Best Practices Back to Docs →