How to Fix "Nginx 504 Gateway Time-out" on Long Running Requests
A request that takes a while to process — a report generation, a large data export, a slow third-party API call — fails with a 504 instead of eventually...
Category
Nginx
Fixes for reverse proxy errors, SSL configuration, and caching issues in Nginx.
How to Resolve "nginx: [emerg] bind() to 0.0.0.0:80 failed (98: Address Already in Use)"
Nginx refuses to start or reload, reporting that port 80 (or whatever port it's configured for) is already claimed by something else. This means another...
How to Fix "Nginx 403 Forbidden" Error on Static File Hosting
Nginx returns a 403 error for a static file you're sure exists and should be publicly accessible. Unlike a 404, this means Nginx found something at that path...
How to Resolve "Nginx SSL Certificate Error: x509: Certificate Signed by Unknown Authority"
A client connecting to your Nginx server over HTTPS rejects the certificate as untrusted, even though you're confident you installed a valid certificate from a...
How to Fix "Nginx proxy_pass Not Forwarding Custom Headers"
Your backend expects a custom header — an API key, a request ID, an Authorization token — but it never arrives, even though the client is clearly sending it...
How to Resolve "Nginx server_name Wildcard Matching Not Working"
You configure a wildcard server_name expecting it to match any subdomain, but requests to those subdomains aren't landing in the block you expect — either...
How to Fix "Nginx Rewrite Rule Causing Infinite Redirect Loop"
A rewrite rule meant to redirect a URL ends up redirecting the browser back to itself over and over, until the browser gives up with a "too many redirects"...
How to Resolve "Nginx Upstream Sent Too Big Header While Reading Response Header"
Nginx rejects a response from your backend because its headers exceed the buffer size Nginx allocated to read them. This is common with large cookies...
Nginx 500 Internal Server Error Without Any Error Log Output
A 500 error with nothing showing up in Nginx's error log doesn't mean Nginx has no idea what happened — it usually means either the log level is set too...