config
HSTS forcing HTTPS causing access issues
Strict-Transport-Security.*max-age|HSTS.*redirect|307.*Internal Redirect
Fixes
- 1.Clear the HSTS cache in browser: chrome://net-internals/#hsts → delete domain
- 2.Ensure HTTPS is fully working before enabling HSTS — once set, browsers won't use HTTP
- 3.Start with a short max-age (300) for testing, then increase to 31536000 for production
sslHSTSredirect
Related Errors
config3 fixes
Nginx 502 Bad Gateway - upstream unavailable
502 Bad Gateway|upstream prematurely closed connection
- •Verify the upstream server is running and listening on the expected address/port
- •Increase proxy_read_timeout and proxy_connect_timeout for slow backends
config3 fixes
Nginx 504 Gateway Timeout
504 Gateway Time-?out|upstream timed out.*reading response
- •Increase proxy_read_timeout (default 60s): proxy_read_timeout 300s
- •Optimize the backend endpoint that's taking too long to respond
config3 fixes
Nginx redirect loop
rewrite or internal redirection cycle|return 301.*too many redirects
- •Check for conflicting rewrite rules that redirect back and forth (HTTP→HTTPS→HTTP)
- •Use 'return 301' instead of 'rewrite' for simple redirects to avoid rule interaction