I was having difficulties with the server serving PHP queries using Unix Sockets for some strange reason. With that said I started to overhaul my configuration and read documentation.
I currently am using the following which is resulting in a 503 Service Unavailable.
Does anybody know how run a Virtualhost on a specific PORT example "9100" using PHP-FPM Daemon as opposed to Unix Sockets?
httpd.conf (FilesMatch):
www.conf (Domain):
Results are 503 Service Unavailable. I want to designate every website on it's individual PORT PHP-FPM daemon; for both uses of Apache 2.4 and NGINX.
Is anyone setup like this and functioning?
I am going for speed and being able to manage hundreds of individual PHP-FPM pools simultaneously.
Thanks!
~TruthSword
I currently am using the following which is resulting in a 503 Service Unavailable.
Does anybody know how run a Virtualhost on a specific PORT example "9100" using PHP-FPM Daemon as opposed to Unix Sockets?
httpd.conf (FilesMatch):
Code:
<FilesMatch "\.php$">
SetHandler "proxy:fcgi://localhost:9100/usr/local/www/apache24/data/website/"
</FilesMatch>
www.conf (Domain):
Code:
[website]
user = www
group = www
listen = 127.0.0.1:9100
listen.owner = www
listen.group = www
listen.mode = 0660
pm = dynamic
pm.max_children = 5
pm.start_servers = 2
pm.min_spare_servers = 1
pm.max_spare_servers = 3
pm.max_requests = 500
request_terminate_timeout = 300
security.limit_extensions = .php
Results are 503 Service Unavailable. I want to designate every website on it's individual PORT PHP-FPM daemon; for both uses of Apache 2.4 and NGINX.
Is anyone setup like this and functioning?
I am going for speed and being able to manage hundreds of individual PHP-FPM pools simultaneously.
Thanks!
~TruthSword