Got it! The problem was absolutely not related to nginx configuration. I found it when I continued to get 502s even with nginx process down O_o I've accidentally added two A-records to the DNS-zone with same name but different IPs. Looks like the resulting IP was chosen in semi-round-robin fashion. And when a not configured server was chosen, I've got those 502s. Whew!… Sorry for disturby nailxx - Nginx Mailing List - English
Hi, all! I've stumbled upon a problem I can't find a solution for many hours in a row. I use nginx as a reverse proxy to python/spawning web-server. I've done it for 1000 times already and all worked fine before this day. Nginx on a server I'm talking about serves 3 separate projects (hostnames) as a reverse proxy. I've added fourth. Three existing projects continued to work perfectly. But tby nailxx - Nginx Mailing List - English