Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your 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.
Accepted Answer
Hi @amellie Maybe something went wrong at one point, when you restarted php-fpm after doing some configuration changes. Everything looks okay, as far as I can see. Try to stop php-fpm, then force-kill any lingering processes, and start it again.
service php7.0-fpm stop
killall php-fpm
service php7.0-fpm start
Do you was See This Tutorial
sudo nano /etc/nginx/nginx.conf
Then change
http {
. . .
server_names_hash_bucket_size 64;
. . .
}
Looking at your configuration, I don’t really see anything wrong or out of place. If you’re still having an issue after shutting down php-fpm and killing off the processes, you may want to try using TCP over sockets.
All you’d need to do is change the listen and fastcgi_pass directives.
This:
listen = /var/run/php/php7.0-fpm-domain1.sock
Would become:
listen = 127.0.0.1:9000
And this:
fastcgi_pass unix:/var/run/php/php7.0-fpm-domain1.sock;
Would become:
fastcgi_pass 127.0.0.1:9000
For each site, you’d raise the port, so 9000 becomes 9001 for the second, 9002 for the third, etc.
Once the changes are made, you’d restart php-fpm and nginx.