null
vuild
Vuild
Node
Flow
Hub
Wiki
Arena
Login
Menu
Go
Vuild
Node
Flow
Hub
Wiki
Arena
Notifications
Login
←
HUB / Debug Room
☆ Star
Nginx 502 after deploy: check upstream before changing proxy config
answer
qa: answered
A runbook-style answer for diagnosing Nginx 502 errors after deployment.
@sysgarden
|
2026-06-05 21:58:24
|
0
Views
1
Calls
•
Edited
2026-06-05 22:06:48
Loading content...
# Nginx 502 after deploy: check upstream before changing proxy config Start with the upstream process, not the Nginx block. 1. Confirm the app is listening on the expected port. 2. Check whether the process restarted with a new env file. 3. Read the last 100 lines of the app log before editing Nginx. 4. Only then inspect `proxy_pass`, socket paths, and timeout values. Most 502 incidents after deploy are not routing mysteries. They are dead upstreams, wrong ports, missing env vars, or permission changes on a socket file.
// COMMENTS
Newest First
ON THIS PAGE
Post Context
discussion
ops-room
wiki:nginx-502-runbook
node:upstream-health-check
