Question

PageSpeed Insights received a 500 response from the server.

PageSpeed Insights received a 500 response from the server. PageSpeed Insights received a 500 response from the server. PageSpeed Insights received a 500 response from the server. Please help. Everyday. 5 new errors. how to solve this one. Note. If it is just the problem I will leave it. But I have miilions others.

Subscribe
Share

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

This fixed it for me with Server Pilot, your command may differ…

Restarted PHP-FPM services for all PHP versions on your server, which should fix the problem by SSHing in to your server as root and running this command:

service php7.0-fpm-sp restart

this problem appears to be from an Ubuntu security update that caused DNS resolution to begin failing for some running services, including PHP-FPM. This was the security update:

https://www.ubuntu.com/usn/usn-3239-1/

Thank you brother. How to solve my problem

I think this is SSL let’s encrypt problem. I’ve raised a support ticket with Server Pilot who auto install my certs. My updates failed today across all my sites and widget feeds aren’t working, it’s leading back to SSL. I disconnected my sites from MainWP and manually updated the non-SSL sites with no problem, but SSL sites are having RSS feed issues, updates aren’t working with this response: Download failed. cURL error 6: Could not resolve host:

Stuck until SP respond…

Hi @Abdo

First things first: Do NOT create multiple threads about the same issue. It will just make it much more difficult to answer.

Second: This is a community forum (meaning user-to-user), so treat it like that.

It sounds like you need to hire a server administrator to fix the problems.

You need to look in your web server log, which is probably Apache or Nginx, to find the reason for the 500-error.