How to Fix ERR_TOO_MANY_REDIRECTS in Webflow
Are you getting the ERR_TOO_MANY_REDIRECTS error when trying to view your Webflow site?
This error means that the page or entire site is in a redirect loop preventing it from being loaded.
In this article, we’ll walk through the steps you can take to identify the issue and resolve this error.
Set the www. Subdomain as the Default Domain
The most common reason for this error on a Webflow site is not having the www. subdomain set as the default domain.
To do this, navigate to the Site Settings, then select the Publishing tab.
In the Production section, select Make default next to the www. version of your domain.
Finally, publish your site to the production domain, then check to see if the error has been resolved.
Check in an Incognito Tab
If you are still seeing ERR_TOO_MANY_REDIRECTS after publishing the default domain change, it may just be a caching issue. Try checking the site in an incognito tab or clearing your cache and reloading the page. If possible, you can also try checking on a device or browser you have not used to view your site yet.
Redirect Chain
If the error is still occurring, we'll need to dig a bit deeper to identify the problem. Paste your URL into the checker at https://httpstatus.io/ to view any redirect chains.
Certain redirects are normal, like if you see a 301 redirect from the root domain to the www. subdomain after setting it as the default. If you don't include https when pasting in the URL, you may also see a redirect from http to https, then another from the root domain to the www. subdomain. These do not mean that you have 301 redirect issue.
If you see additional redirects aside from the ones described above, these can help you identify where the problem is and how to fix it.
For example, FlowCamp's tutorial page previously had the slug /blog, which is now redirected to /webflow-tutorials in the Site Settings. If we accidentally added a redirect from /webflow-tutorials to /blog, the page would get stuck in a redirect loop and throw an error. Even if you don’t think you’ve set up a redirect like this, it’s worth double checking as Webflow may create redirects for you when you rename a page.
Check 301 Redirects
If you find a 301 redirect issue like the one described above when using the httpstatus checker, you can update your site’s 301 redirects in the Site Settings.
To do this, navigate to the Site Settings, then select the Publishing tab.
Scroll down to the 301 redirects section, then locate the redirect you need to remove.
Hover over the redirect you’d like to remove, then click the trash icon to Delete the redirect.
Use a DNS Propagation Checker
If the error is not resolved after following the steps above, it is most likely a DNS propagation issue that may just require waiting 24 - 48 hours. DNS propagation is the time it takes for changes made to DNS records to take effect across the Internet.
To be more confident that you just need to wait it out, you can check the current status of DNS records using a DNS Checker like https://dnschecker.org/.
To use the DNS checker, start by just entering your root domain without the www. and check the A records. The below image shows an example of the results you want to see for a Webflow site.
Next, enter www. version of your subdomain, and update the dropdown to check the CNAME records below. Ideally, the results should all show proxy-ssl.webflow.com.
If you see varying results between different locations, this is a sign that the DNS propagation is still in progress and waiting 24 - 48 hours will most likely resolve the issue.
If the results you see don’t match the DNS records you have set, this is another sign that you may just need to wait for DNS propagation to finish, but you should also double check that your DNS records are set correctly.
We hope this article has helped you resolve the ERR_TOO_MANY_REDIRECTS error. You might also want to check out our articles on How to Contact Webflow Support and How to Transfer a Webflow Site.
If you liked this article, then please subscribe to our newsletter or follow us on X.