Thanks for sharing.

Thanks for the info.

Good information to know. Thanks for sharing.

Doris

Hey Peter, a 502, is when a web server that is acting as a gateway or proxy server, gets an invalid/no response and content is not yet cached, from one of the upstream servers, there are a number things that can cause this.

Nginx is the web server type, and the ubuntu text is the operating version/os that Nginx is running on so we have Nginx v1.4.6 running on Ubuntu (Linux)

Nginx is often used as a proxy/front edge/load balancing server with another web server or a cluster of web servers behind it, so if the front edge web server cannot get a valid response from 'backend' aka, the source servers, then one of the messages you can get is a 502.

As labman says, could be an update, either by WA or by Amazon on the WA clusters or a few other things, such as garbage collection/disposal of cached pages and recreation of cache and super cache, just depends on when your request hits the server during its process.

It is usually fairly short-lived generally, and I see it fairly regularly from here in the UK, you just have to keep trying, as there is not really anything you can do about things like 502.

Regards

Neil

It happens...not a biggie...it's rather like gas...it goes away quickly...

That happens sometimes when WA is doing a background update. They usually don't last long while the update loads in the background.