Richard, We started using nginx fairly recently and I immediately noticed that nginx will throw a 502 when it should probably be throwing a 503 (service unavailable). It does this when it first comes up and there are no upstream servers (or "backends" in haproxy speak) registered with it. Most other LB software would throw a 503, not a 502. I actually put this in our nginx.conf to override that behavior (since we have a custom 503 error page): error_page 502 =503 /503.html;
Let me know if you have any other questions about nginx, I might be able to help.. Jeremy On Wednesday, January 9, 2013 5:38:37 AM UTC-8, RichBos wrote: > > Hi, just wondered if anyone else has had this error? > > We're getting Error 502 Bad Gateway on our NGINX load balancer, tried a > different instance (10.04 instead of 12.04) and it's still the same, as > such we're presuming it's a problem app side (we're running x2 LAMP > instances) but have no idea what or why? > > Any pointers appreciated....! > > Richard. > -- You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
