How do I troubleshoot a persistent five-hundred-and-two bad gateway error in Nginx when acting as a reverse proxy for a Node.js application that occasionally crashes under heavy traffic spikes?
Download run
Fan-out diagram
The searches the AI actually ran for this prompt.
SEED QUERY
How do I troubleshoot a persistent five-hundred-and-two bad gateway error in Nginx when acting as a reverse proxy for a Node.js application that occasionally crashes under heavy traffic spikes?
1 real search · 1 real-search pass
official Nginx documentation proxy_read_timeout upstream errors Node.js process memory usage diagnostics PM2 restart memory limit graceful shutdown clusterGoogle ↗
OBSERVEDReason
Badge and edge weight = share of passes that produced the query. Hover a query for its intent and routing format.
Query classes
Google's semantic query class for every sub-query: what kind of answer each search is after, simulated vs real.
ChatGPT real searches (1)
Classes come from the query-classifier (a local Laya model). 1 of 1 calls are low-confidence (under 50%) — hover a query in the table to see its confidence.
Searches and sources
ChatGPT1 real searches · gpt-6
official Nginx documentation proxy_read_timeout upstream errors Node.js process memory usage diagnostics PM2 restart memory limit graceful shutdown cluster Google ↗
- Memory Threshold Auto Reload | Features · pm2.io
- PM2 · pm2.keymetrics.io
- PM2 · pm2.keymetrics.io
- Graceful Shutdown | Best Practices · pm2.io