I just installed ISPConfig 22.214.171.124, with nginx, on a brand new box. Immediately after finishing the ISPConfig installation, I attempted to access the interface at https://example.com:8080, and received "502 Bad Gateway". A quick look at the log file (/etc/nginx/error.log) reveals the reason: Code: 2014/07/23 20:54:10 [error] 4580#0: *8 connect() to unix:/var/lib/php5-fpm/ispconfig.sock failed (111: Connection refused) while connecting to upstream, client: 126.96.36.199, server: _, request: "GET / HTTP/1.1", upstream: "fastcgi://unix:/var/lib/php5-fpm/ispconfig.sock:", host: "example.com:8080" The socket file referenced in the ISPConfig vhost (/etc/nginx/sites-available/ispconfig.vhost [line 28]) references the following socket: Code: fastcgi_pass unix:/var/lib/php5-fpm/ispconfig.sock; Yet, the socket file does not actually exist on the filesystem. Is this a known issue? Am I supposed to create the socket file manually? Just trying to determine whether or not I should open a bug report. Surely, others have run into this. Thanks! UPDATE: Huh! After about 10 minutes, the socket file appeared at the expected location, /var/lib/php5-fpm/ispconfig.sock. I'm sure there is some "good reason" for the delay. But, I'm still seeing an error. The original error Code: connect() to unix:/var/lib/php5-fpm/ispconfig.sock failed (2: No such file or directory) changed to the following, once the socket file mysteriously showed-up Code: connect() to unix:/var/lib/php5-fpm/ispconfig.sock failed (111: Connection refused) Here are the socket details: Code: # stat /var/lib/php5-fpm/ispconfig.sock File: â/var/lib/php5-fpm/ispconfig.sockâ Size: 0 Blocks: 0 IO Block: 4096 socket Device: ca01h/51713d Inode: 1632266 Links: 1 Access: (0660/srw-rw----) Uid: ( 5003/ispconfig) Gid: ( 5004/ispconfig) Access: 2014-07-23 21:00:53.696859916 +0000 Modify: 2014-07-23 21:00:53.696859916 +0000 Change: 2014-07-23 21:00:53.696859916 +0000 Birth: - Thanks for any ideas! UPDATE 2: I restarted the box and now everything works. Maybe the php5-fpm service had not been started (or failed to restart), or something along those lines. Sooo... never mind. Maybe this will help someone else that gets trigger-happy immediately after a fresh installation. UPDATE 3: I had actually installed ISPConfig 188.8.131.52 (not 184.108.40.206 as stated above). I later realized the reason: ISPConfig 220.127.116.11 is listed as the latest version at http://www.ispconfig.org/files/file/2-ispconfig/ . Should this be changed to 18.104.22.168?