Mini server and laptop showing an Nginx Proxy Manager dashboard

REVERSE PROXY AND HTTPS

Nginx Proxy Manager shows a 502?

Check whether the upstream service is reachable before blaming the certificate, then verify HTTPS for one hostname and one service.

  • One hostname and one upstream service
  • Upstream checked before certificate changes
  • HTTPS verified from a client browser

THE THREE FAILURES WE SEE

What is going wrong?

01

502 Bad Gateway

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

02

Certificate warning

HTTPS loads with a name mismatch, expired certificate, or untrusted issuer warning.

03

Works by IP, not hostname

The service is reachable on the LAN address but not through the proxy hostname.

HOW WE TEST

Find the failing layer, then prove the fix.

  1. Test the upstream directly. From the proxy container or host, request the service by its internal IP and port. If that fails, fix the service before touching TLS.
  2. Confirm DNS and proxy host. Check that the hostname points to the proxy and that the proxy host's forward hostname, port, and scheme match the service.
  3. Inspect the certificate. Confirm the certificate covers the exact hostname and is not expired. A valid certificate cannot fix an unreachable upstream.
  4. Verify from a client. Open the HTTPS URL in a clean browser profile, check the certificate chain, and confirm the expected application loads.
A laptop displaying proxy host settings and a browser HTTPS test
HTTPS is only finished when the hostname reaches the intended service with a valid certificate.

SERVICE SCOPE

What is included

Included

  • One hostname and one upstream service
  • DNS, proxy host, and upstream checks
  • Certificate and HTTPS verification
  • Rollback notes for proxy changes

Not included

  • Issuing a paid certificate
  • Building a new application
  • Router or ISP changes without approval
  • Guaranteeing third-party DNS propagation time

The session covers one agreed device and one verified path. Anything outside the written scope is quoted separately before work starts.

FAQ

Before you book

Is a 502 always a certificate problem?

No. A 502 usually means the proxy cannot reach or get a valid response from the upstream; TLS is a separate layer.

Can you fix my DNS?

We verify the DNS record and explain the required change. The domain owner makes the actual registrar or DNS edit.

Will you restart my whole server?

Only the specific service or proxy component after approval, and only when the evidence points there.

NEXT STEP

Tell us what is happening.

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

Nginx Proxy Manager SSL Help Guides

All guides