Error 502 Bad Gateway

[webcreative24]

Hi. I have installed Magento 2 website. On the main page, I have a lot of images. when I open the site it takes a very long time to load and after a couple of minutes when I refresh the page I get a 502 Bad Gateway error and the site does not open again until I restart php. did you encounter this problem before?
MacBook Pro M1
PHP Monitor Version 5.7.4
Laravel Valet 3.3.2
Mac OS Ventura
Video attached:
https://monosnap.com/file/jyr3VKmacP6n0TL0dpbM7878Q8eR7d

[nicoverbruggen]

If the page takes a long time to load, that sounds like a timeout issue somewhere.

NGINX will return a 502 Bad Gateway error if it can’t successfully proxy a request to PHP-FPM, or if PHP-FPM fails to respond.

You may want to look in ~/.config/valet/Log/php-fpm.log and ~/.config/valet/Log/nginx-error.log and see what's in there. That might give you more of a clue.

Some PHP script (or site) is likely slow (something that loads asynchronously can be a common cause that isn't immediately obvious), and is potentially hogging all of php-fpm. As a result, restarting php-fpm will fix this issue until you bump into the problem again... so PHP Monitor works correctly in this case.

You will want to look at the underlying cause of this timeout, as this is indeed very inconvenient. I've been there!

If you're looking to track down such performance issues, I recommend taking the time to set up Xdebug. It's a bit tricky to set up at first, but it's the most powerful tool to identify slowdown in your apps/sites. I've had good experiences with PhpStorm's profiling integration. For more info, see: https://www.jetbrains.com/help/phpstorm/profiling-with-xdebug.html

Another common cause of 502 errors is conflicting PHP-FPM processes: usually the php-fpm.log contains a line like Another FPM instance seems to already listen to ..., but those are usually sorted out after restarting your system and starting PHP Monitor again, so you can try that too.

Hope that helps!