![NGINX 502 Bad Gateway Connect() failed (133: No route to host) while connecting to up stream - Server Fault NGINX 502 Bad Gateway Connect() failed (133: No route to host) while connecting to up stream - Server Fault](https://i.stack.imgur.com/eNGat.jpg?s=64&g=1)
NGINX 502 Bad Gateway Connect() failed (133: No route to host) while connecting to up stream - Server Fault
failed (113: No route to host) while connecting to upstream" when trying to reverse proxy Sonarr · Issue #1348 · nginx-proxy/nginx-proxy · GitHub
connect() failed (113: No route to host) while connecting to upstream · Issue #1796 · dokku/dokku · GitHub
![thru hike Archives - Seeking Lost: Thru-Hiking & Backpacking Adventures Seeking Lost: Thru-Hiking & Backpacking Adventures thru hike Archives - Seeking Lost: Thru-Hiking & Backpacking Adventures Seeking Lost: Thru-Hiking & Backpacking Adventures](https://seekinglost.com/wp-content/uploads/2022/04/MST-Route-Overview-Map-625-Miles-580x393.jpg)