2 months ago
I need to clear the cache it says 200 but in the browser: This page isn’t working
www.hoosiercladding.com redirected you too many times.
ERR_TOO_MANY_REDIRECTS
Pinned Solution
2 months ago
Hey! This ERR_TOO_MANY_REDIRECTS error is typically a configuration issue rather than a cache problem. The most common cause on Railway is an HTTP to HTTPS redirect loop - if your app is forcing HTTPS redirects but Railway’s proxy already handles SSL termination, you’ll get this loop. Your app should accept HTTP traffic since Railway handles the SSL at the edge. Another frequent culprit is Cloudflare configuration - if you’re using it, change your SSL/TLS mode from “Flexible” to “Full” or “Full (Strict)” in the Cloudflare dashboard. Also check for any application-level redirect rules in your code, .htaccess files, or web server config that might conflict. To debug, try accessing your Railway domain (*.up.railway.app) directly to see if it works there, check your Railway logs for redirect patterns, and temporarily disable any HTTPS redirect code in your app. If you’re using a specific framework like Django, look for settings like SECURE_SSL_REDIRECT and set it to False since Railway handles the SSL. What framework or platform are you running?
3 Replies
2 months ago
Hiya,
It looks like this is a client side issue. I was able to load your endpoint just fine.
I took a look at your deployment and didn't see any errors either. Can you try clearing your browser's cache and trying again?
Status changed to Awaiting User Response Railway • 2 months ago
2 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 2 months ago
2 months ago
Hey! This ERR_TOO_MANY_REDIRECTS error is typically a configuration issue rather than a cache problem. The most common cause on Railway is an HTTP to HTTPS redirect loop - if your app is forcing HTTPS redirects but Railway’s proxy already handles SSL termination, you’ll get this loop. Your app should accept HTTP traffic since Railway handles the SSL at the edge. Another frequent culprit is Cloudflare configuration - if you’re using it, change your SSL/TLS mode from “Flexible” to “Full” or “Full (Strict)” in the Cloudflare dashboard. Also check for any application-level redirect rules in your code, .htaccess files, or web server config that might conflict. To debug, try accessing your Railway domain (*.up.railway.app) directly to see if it works there, check your Railway logs for redirect patterns, and temporarily disable any HTTPS redirect code in your app. If you’re using a specific framework like Django, look for settings like SECURE_SSL_REDIRECT and set it to False since Railway handles the SSL. What framework or platform are you running?
Status changed to Solved noahd • 2 months ago
