The Good: On the panel server I can still create a new website through the ISPConfig console as normal. Using an NGINX (release 9) webserver with php-fpm and the option to use a socket - it creates the php5/fpm/pool.d *.conf file and corresponding nginx/sites-available *.vhost as expected, with the two tied together through their reference of a /var/lib/php5-fpm/*.sock The Bad: On a dedicated server for websites in the ISPConfig multi-server cluster, using the same options as above, this no longer happens. What I get is NO /etc/nginx/sites-*/*.vhost file created AND a /etc/php5/fpm/pool.d/*.conf for the website BUT no longer using a socket; instead, I get: Code: listen = 127.0.0.1:**** listen.allowed_clients = 127.0.0.1 How would I look into solving this? Possible Scenario I recently upgraded all my ISPConfig3 servers in the cluster to 18.104.22.168p9. At the same time (possible just before) I upgraded the NGINX webserver on this troubled server that I am having problems with. I had to blow out the old NGINX configurations (purged) and then I reinstalled them. I noticed that the new NGINX server did not come with the sites-available / sites-enabled pair of directories and instead was wanting to use a simple conf.d daemon directory which it referenced with an include statement from within /etc/nginx/nginx.conf Unsure of how ISPConfig would be able to deal with missing sites-* directories (and having since tested and failed without them) I put them in manually. Existing sites ran fine, but the above problem now exists on any attempt to build new sites - and old sites get damaged if/when the ISPConfig3 panel is pushed to rebuild the files in those directories. Any guidance would be appreciated.