DNS Redirection Loop

1

Hi. I’ve followed the custom domain process and still cannot make it work.
I have Network Solutions as my DNS provider

I’ve added:

  1. “A” record for * and @ pointing to 216.24.57.1
  2. “CNAME” record for www to my URL on Render

Render is able to verify the same too.

  • Domain Verified
  • Certificate Issued

Domain Verified
Certificate Issued

However, I get stuck in a DNS redirection loop:
This page isn’t working

**** redirected you too many times.

ERR_TOO_MANY_REDIRECTS

Please help.

1 Like
2

It would be worth checking which custom domain you added first - you can do this in the dashboard under settings > custom domains. (The one you can delete is the explicit one you added)

If you added www.mysite.com first then we would be redirecting mysite.com to www.mysite.com, if you added mysite.com first then www.mysite.com would redirect to mysite.com. If you need to reverse the redirection you need to delete the custom domain and add it the other way around.

Based on this, your application may be redirecting in the opposite way, so for example, if we redirect mysite.com → www.mysite.com and then the request arrives at your service and it redirects www.mysite.com → mysite.com then you end up in this redirection loop.

3

I am having the same problem. I have tried the solution @John_B suggested and it doesn’t seem to matter if I set up the custom domain with the www.myURL.com or just myURL.com, the infinite redirect keeps happening.

Also I am using Domain . com as my registrar.

4

I’d really suggest dropping down to using curl to inspect the headers to see what’s happening - browser caching redirects can really hide actual behaviour.

5

The ERR_TOO_MANY_REDIRECTS issue usually comes from an HTTPS/redirect misconfiguration.

6

I also encountered the same situation

7

You’re getting the ERR_TOO_MANY_REDIRECTS likely because both Render and your DNS setup are redirecting www to non-www (or vice versa) repeatedly. To fix it, go to your Render Custom Domains settings and choose either www or non-www as the primary domain, then redirect the other one to it (not both ways). Also, ensure your DNS settings only point one version (e.g., www) via CNAME and the root (@) via A record, without circular redirection. Clear browser cookies and cache after changes.

Thanks You
Warriors

1 Like
8

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.