Case Study: 502 Bad Gateway

One of the applications hosted on our platform started returning a 502 Bad Gateway out of nowhere. A 502 Bad Gateway response code usually means that either the PHP-FPM pool has crashed and cannot be connected to, or all the workers are occupied by long-running code, deadlocks, I/O blocks. Within minutes our team was investigating…

Continue reading →