connect() failed (111: Connection refused) on Nginx in front of a Node app. Where now?
@luckyfiddler wowww ok the socket path changed after a PHP update and teh Nginx config still pointed at the old one. Updated fastcgi_pass, reloaded, done. Embarrassing, but fixed. u guys are the best!!!
hunting one stray http:// link across a laravel app. tips?
Related topics
- Is A 502 Every Few Hours At Random My Hosts Fault Or MINE?
- my site goes 502 right after every deploy. proxy or app to blame?
- Is A 502 Whenever Someone Uploads A Big File My Hosts Fault Or MINE?
- why does apache proxying to gunicorn throw 502s only during traffic spikes?
- is it nginx or the spring boot app? a 502 mystery with one clue
- 502 Bad Gateway Right After I Enabled HTTPS, But The Django App Swears Its Up
Reply to this topic
Sign in or create an account to reply.