Too many redirects
Would anyone know what would be causing "too many redirects" when I try to visit my subdomain? I'm using "Full" as my encryption mode in the dashboard.
13 Replies
Support AI
According to the documentation, if your domain's encryption mode is set to Full (https://developers.cloudflare.com/ssl/origin-configuration/ssl-modes/full/), Cloudflare sends encrypted requests to your origin server over HTTPS. Redirect loops will occur if your origin server automatically redirects all HTTPS requests to HTTP.
To solve this issue, you can try removing HTTP redirects from your origin server. You can check your origin server's configuration to see if there are any redirects set up that might be causing the loop.
Additionally, you can also check if you have any Page Rules or URL redirects set up in Cloudflare that might be conflicting with each other and causing the redirect loop.
You can refer to the documentation for more information on troubleshooting "too many redirects" errors: https://developers.cloudflare.com/ssl/troubleshooting/too-many-redirects/
This is an AI generated response, it may not be 100% accurate. Please validate the output. You can ask followups by replying to this message or mentioning me.
Which should I disable?
I just tried using Full(strict) and same thing. Does it take awhile for things to propagate when changing this and I just need to be patient?
what's the subdomain?
It correctly points to my internal IP address 192.168.1.3.
That's a private IP, your CF settings don't play any role
Oh, okay good. I just wanted to make sure it wasn't a CF thing as I'm not very educated on that side of things. I'll investigate the Nginx Proxy Manager side of things as that's about the only other thing I can think would be the issue here.
Is the site supposed to be only available on your local network?
Yes, I'm trying to use Let's Encrypt for SSL on my internal network for things like Kasm that will be used internally.
If you're not using port 443, you need to type in the port every time.
I've never used nginx proxy manager. But if you have nginx listening on 443, you'll want to check it's configuration.
It's listening on 9443 currently.
then you still need to type in the port 9443^^
Yeah, I think I'm going to investigate npm further. I'm kind of relieved it's not a CF issue as I was dreading on troubleshooting that 🙂 Thanks for your help 🙂