Vovy traces the redirect loop between your host, Cloudflare and your app, finds the setting fighting the others, and fixes it so the page loads.
My site says ERR_TOO_MANY_REDIRECTS after I added my domain, fix it
How it works
- Reproduce the loop: Vovy loads your site in Chrome and records every hop, so you can see the address bouncing between http and https, or www and the bare domain.
- Check Cloudflare SSL mode: The usual cause: Cloudflare set to Flexible while your host already forces HTTPS. Each side keeps sending the visitor back to the other.
- Check your host's domain redirects: Vovy opens your Vercel domain settings and looks for www and the root domain redirecting to each other.
- Switch to Full (strict) SSL: Vovy changes Cloudflare to Full (strict) so both sides agree on HTTPS. This touches live traffic, so it asks you first.
- Confirm the site loads: Vovy reloads your domain with and without www in a fresh window, then shows the clean one-hop chain on a card.
What you provide
- Your domain name
- Access to Cloudflare and your host
What you get
- A site that loads again
- The redirect chain, before and after
- The one setting that caused it, explained
FAQ
Why did this start after I added Cloudflare?
Cloudflare's Flexible SSL talks to your host over plain http. If your host redirects http to https, the two loop forever. Full (strict) fixes it.
Will visitors see downtime while this is fixed?
The site already fails to load during a loop, so the change only helps. Browsers can cache the bad redirect for a few minutes, so test in a private window.
Can my app code cause this too?
Yes. Middleware that forces a login or a trailing slash can loop. Vovy checks the host and DNS first, then the redirect rules in your code.
Related tasks
All tasks