I'm running ISPConfig 2.2.32 on CentOS 5.3. I've been running without any problems, but I just updated ssh and now the ISPConfig control panel will not load. Any ideas what might be wrong? Steps I took: 1. yum update php (version 5.2.9 is now installed) 2. service httpd restart (this gave me an error starting back up) 3. restarted the whole server 4. httpd is now running and can restart without error 5. I can access all websites fine. php seems to be working fine. 6. Tried to open the control panel (ie. https://192.168.2.2:81) and I get an error saying "Failed to Connect", "Firefox can't establish a connection to the server at 192.168.2.2:81" Any ideas what is causing this problem? Are there some trouble shooting steps I can take to see if the ISPConfig web server is up? Is there a chance the SSL got messed up when I did the PHP update? Also, I did make sure the firewall isn't blocking port 81. Everything was working perfect before I did the php update. Thanks in advance, JD
I'd just like to add... ISPConfig is running. I just ran: # service ispconfig_server start Starting ISPConfig system... /root/ispconfig/httpd/bin/apachectl startssl: httpd (pid 14534) already running FreshClam is already running! ISPConfig system is now up and running! I can't access from the web browser though.
Is SELinux switched off? Have you tried to stop the firewall? What's the output of Code: netstat -tap ?
Thanks for your response. I tried accessing the control panel again today and got a different error in my web browser. This time I got a Secure Connection failed. It said something about the length of a token or something. I can't remember what it specifically said. It was NOT the typical untrusted certificate error that happens sometimes. I confirmed that both iptables and selinux was off. They were. After that, I decided to reboot once more, just to make sure any changes I had made are in affect. After the reboot (which was actually my 3rd reboot since upgrading php), the control panel loaded. I was able to login now without any problems. Any ideas what the problem might have been? I have to upgrade another server next weekend and am hoping to avoid the same problems. ### Here's the output of netstat -tap before doing this last reboot: [root@tyson ~]# netstat -tap Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:5666 *:* LISTEN 2326/nrpe tcp 0 0 tyson.mydomain.com:10024 *:* LISTEN 2311/amavisd (maste tcp 0 0 *:mysql *:* LISTEN 2241/mysqld tcp 0 0 *:sunrpc *:* LISTEN 1822/portmap tcp 0 0 *:hosts2-ns *:* LISTEN 14534/ispconfig_htt tcp 0 0 tyson.mydomain.com:ipp *:* LISTEN 2115/cupsd tcp 0 0 *:smtp *:* LISTEN 24365/master tcp 0 0 *:rxe *:* LISTEN 1851/rpc.statd tcp 0 0 *:http *:* LISTEN 1604/httpd tcp 0 0 *:ftp *:* LISTEN 24280/proftpd: (acc tcp 0 0 *:ssh *:* LISTEN 2100/sshd tcp 0 1184 tyson.mydomain.com:ssh 24-148-8-145.mart-bsr:58018 ESTABLISHED 22135/sshd: jglick ### Here's the output of netstat -tap after doing this last reboot: [root@tyson ~]# netstat -tap Active Internet connections (servers and established) Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name tcp 0 0 *:5666 *:* LISTEN 2336/nrpe tcp 0 0 tyson.mydomain.com:10024 *:* LISTEN 2321/amavisd (maste tcp 0 0 *:mysql *:* LISTEN 2242/mysqld tcp 0 0 *:sunrpc *:* LISTEN 1823/portmap tcp 0 0 *:hosts2-ns *:* LISTEN 2741/ispconfig_http tcp 0 0 tyson.mydomain.com:ipp *:* LISTEN 2116/cupsd tcp 0 0 *:smtp *:* LISTEN 2856/master tcp 0 0 *:quotad *:* LISTEN 1852/rpc.statd tcp 0 0 *:imaps *:* LISTEN 2276/dovecot tcp 0 0 *op3s *:* LISTEN 2276/dovecot tcp 0 0 *op3 *:* LISTEN 2276/dovecot tcp 0 0 *:imap *:* LISTEN 2276/dovecot tcp 0 0 *:http *:* LISTEN 2772/httpd tcp 0 0 *:ftp *:* LISTEN 2907/proftpd: (acce tcp 0 0 *:ssh *:* LISTEN 2101/sshd tcp 0 1184 tyson.mydomain.com:ssh 24-148-8-145.mart-bsr:58868 ESTABLISHED 3094/sshd: jglick [
