01
502 Bad Gateway
The proxy host resolves, but the browser returns 502 or 504 instead of the service.

THE THREE FAILURES WE SEE
01
The proxy host resolves, but the browser returns 502 or 504 instead of the service.
02
HTTPS loads with a name mismatch, expired certificate, or untrusted issuer warning.
03
The service is reachable on the LAN address but not through the proxy hostname.
HOW WE TEST

SERVICE SCOPE
The session covers one agreed device and one verified path. Anything outside the written scope is quoted separately before work starts.
FAQ
No. A 502 usually means the proxy cannot reach or get a valid response from the upstream; TLS is a separate layer.
We verify the DNS record and explain the required change. The domain owner makes the actual registrar or DNS edit.
Only the specific service or proxy component after approval, and only when the evidence points there.
NEXT STEP
Send the device, software, exact symptom, and what you have already tried. We will confirm scope and a fixed quote before booking.
No passwords. A real reply comes from [email protected].
FROM THE BLOG
Fix a 502 after restart when your upstream service runs fine on its direct port. Check the WebSocket Upgrade header in Nginx Proxy Manager and verify with a controlled test.
Certificate exists in NPM but browser shows trust or handshake error. Follow these checks to diagnose the renewal mismatch and restore trust.
Certificate issuance stops at DNS validation because your DNS provider never accepts the TXT record. Check API credentials, zone scope, and propagation with a direct query, then roll back safely.
Troubleshoot an Nginx Proxy Manager HTTPS redirect loop by isolating whether NPM or the backend forces the redirect, with a verification test and rollback note.
Certificate exists in NPM but the browser still shows a trust or handshake error? Check the Proxy Host's SSL tab, confirm the right certificate is selected, and verify with a direct TLS test.
After a restart, your Nginx Proxy Manager proxy host returns 502 even though the upstream service runs on its direct port. Check the upstream scheme setting to resolve this specific 502.
Proxy host returns 502 after restart even though the upstream service runs on its direct port. Check the upstream listening address and fix the mismatch.
Troubleshoot an nginx proxy manager hsts redirect loop causing too many redirects. Check HSTS headers, force SSL settings, and verify with curl.
Certificate issuance stalls at DNS validation because Cloudflare rejects the TXT record. Check API token permissions, zone ID, and propagation with these steps.
Troubleshoot nginx proxy manager ssl handshake failed when the certificate is issued but the browser still shows a trust error. Step-by-step checks and verification.