Plesk & httpd socket conflict

[Skip Dreibelbis]

It seems somewhere there is a misconfiguration in my installation. When I do a 'service psa start' I have access to the panel, but httpd can't start, complaining via ssl_module that make_sock failed on port 8443. If I do a 'service psa stop' and then start httpd, my sites work but the panel doesn't.

Where do I need to look for the configuration? I've looked at httpd.conf and ssl.conf in /etc/httpd but they didn't have anything regarding port 8443.

 

[IgorG]

# grep 8443 /etc/sw-cp-server/applications.d/plesk.conf
$SERVER["socket"] == ":8443" {

 

[Skip Dreibelbis]

The grep command as written above does return the appropriate line in the plesk.conf, however there must be another line somewhere that is causing the issue as seen below.

$ cd /etc/sw-cp-server/applications.d/
[applications.d]$ grep 8443 plesk.conf
$SERVER["socket"] == ":8443" {

[root~]# service httpd stop && service psa start
Stopping httpd: [ OK ]
Starting psa... done
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Plesk: Starting Mail Server... already started
[Mon Mar 14 05:39:10 2011] [warn] module ssl_module is already loaded, skipping
(98)Address already in use: make_sock: could not bind to address [::]:8443
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:8443
no listening sockets available, shutting down
Unable to open logs
websrvmng: Service /etc/init.d/httpd failed to start
websrvmng: Service /etc/init.d/httpd failed to start
Starting mail handlers tmpfs storage
Starting psa... done

[root~]# service psa stop && service httpd start && service psa start
Stopping psa... done
Stopping mail handlers tmpfs storage
Starting httpd: [Mon Mar 14 05:39:42 2011] [warn] module ssl_module is already loaded, skipping
[ OK ]
Starting psa... failed
Starting xinetd service... done
Starting named service... done
Starting mysqld service... done
Starting postgresql service... done
Starting psa-spamassassin service... done
Plesk: Starting Mail Server... already started
Starting mail handlers tmpfs storage
Starting psa... failed

 

[IgorG]

Try to stop sw-cp-server and check what is the process which has opened port 8443 with

# lsof -i tcp:8443

 

[Skip Dreibelbis]

With httpd running and psa stopped I have the following output

[root~]# lsof -i tcp8443
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
httpd 27287 root 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27345 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27373 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27374 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27375 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27377 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27380 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27382 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27384 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27385 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27525 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27528 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27529 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27530 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 27835 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 28576 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)
httpd 28896 apache 6u IPv6 2506776 TCP pcsync-https (LISTEN)


With httpd stopped and psa running I have the following output


[root~]# lsof -i tcp8443
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
sw-cp-ser 12652 sw-cp-server 7u IPv4 2752911 TCP pcsync-https (LISTEN)

 

[IgorG]

I think that you should check httpd config files for 8443 port mentions.

 

[Skip Dreibelbis]

I think I've found it. I had looked at the ssl.conf but the following command found it in nss.conf.

[root~]# grep 8443 /etc/httpd/conf/httpd.conf
[root~]# grep 8443 /etc/httpd/conf.d/*
/etc/httpd/conf.d/nss.conf:# Listen directives: "Listen [::]:8443" and "Listen 0.0.0.0:443"
/etc/httpd/conf.d/nss.conf:Listen 8443
/etc/httpd/conf.d/nss.conf:<VirtualHost _default_:8443>
/etc/httpd/conf.d/nss.conf:#ServerName www.example.com:8443

 

[Skip Dreibelbis]

Apparently nss.conf isn't the correct location. When I commented the listen directive the services started properly, but the Plesk panel could not be displayed. This box did have version 9.6 prior to 10.1.1 as I needed it to complete a migration from 8.2 to 10.1.1. Could there be some residual files left from 9.6 that are causing the issue?

 

[Skip Dreibelbis]

Alright, nss.conf is the correct location to comment the port. The issue is that the port was being blocked at my office. Since our server has multiple ip addresses I previously had the firewall (iptables) configured to reroute traffic from port 443 to 8443, so along with a DNS entry this allowed us to have URLs like https://plesk.domain.name.

I think I saw somewhere in a php file that there was some URL rewriting happening. Is there any way to stop Plesk from rewriting the URL to https://plesk.domain.name:8443 now that we're on version 10.1.1?