Solved Apache & php

[VladiBG]

Hope can I tell if I have set up sockets correctly?

ls -l /var/run/php-fpm.sock does not find anything. Should it get created when you start fpm?

Yes the socket is created when the php-fpm is started.

ssl_module is for https when you have valid SSL certificate
socache_shmcb_module is shared cache provider if you don't plan to use it don't enable it.

 

[balanga]

Yes the socket is created when the php-fpm is started.

Thanks for that. It looks like my update to /usr/local/etc/php-fpm.d/www.conf wasn't done properly.

I've changed it, restarted and it exists now.

 

[Alain De Vos]

There are people who claim, socket more secure than a port on 127.0.0.1. But then 127.0.0.1 is not routable

 

[Espionage724]

There are people who claim, socket more secure than a port on 127.0.0.1.

Maybe file permissions vs network stack security?

Can things reading on localhost see other things? (not sure how to word that better but can nginx see PHP-FPM on 127.0.0.1:9002 if only 9001 is specified in a nginx conf, or able to see a random game server on 8083? is stuff on localhost isolated or free-for-all readable?)

Using sockets might imply trusting the OS's file permissions handling while localhost trusts the network stack. I like the idea of localhost more when running services are all trusted (I'd also rather not guess chmod for sockets and hope it's good ) but heard something like file access to sockets being faster than localhost (maybe a disk IO/cache/RAM fetch is faster than CPU localhost query?)