Issue Apache and sw-cp-server uses the same ports (8443)

[andreas.scherer]

Server operating system version

Centos 7.9

Plesk version and microupdate number

Obsidian 18.0.49

Hi All!
After I made the correct DNS setting for all domains, I was able to start everything clean with the original configuration.
Sorry for the "unnecessary" traffic here. Maybe an admin can delete the issue thread here.
Is just a suggestion!

 

[Peter Debik]

Yes, we could delete it, but it would be even better if we had the original edit and the solution in the thread. There is absolutely no problem with describing an issue. And even better if you find the solution and post it here so that other users, me included, can learn from it. IT means constant learning, and we all much appreciate contributions from users like you, because it gives us more insight how we can improve the product and improve the service. Please feel free to explain issues and also your thoughts along a thread.

 

[andreas.scherer]

Unfortunately, Obsidian only lasted 3 hours. Now it has the same problem again.
Why does sw-cp-server occupy the ipv6 port 8443?
The httpd listens on this port.
As far as I understand nginx is listening on port 80 and 443.
The sw-cp-server should be listening on the ipv4 address port 8443.
Apache (httpd) should actually only be called from nginx. Or am I confusing something?

Perhaps someone could explain these relationships in detail.

Thanks in advance
Andreas

 

[Peter Debik]

With Nginx enabled:
Nginx listens to 80, 443
Apache listens to 7080, 7081 (this is where Nginx communicates with Apache)

With Nginx disabled:
Apache listens to 80, 443

The internal Plesk engine listens to 8443 and 8447. Apache must not listen to 8443 at any time. If it does, there may be something wrong with web server configuration templates. Have they been modified (custom templates)?

 

[andreas.scherer]

No, the templates are as it where installed.
If nginx is enabled nginx should catch all traffic and send it to apache or the plesk-engine. IMHO

 

[Peter Debik]

Yes, but in your case Apache seems to grab port 8443. And that cannot be the case when the original web server configuration templates are being used. Have you tried this?
# plesk repair web

 

[andreas.scherer]

Let's giv us a try!

[root@andreas ~]# plesk repair web
Checking Plesk version .............................................. [OK]
Checking for custom configuration templates ......................... [OK]
Checking associations between domains and IP addresses .............. [OK]
Checking for corrupted reference between IP collections and IPaddresses
..................................................................... [OK]
Checking for links between APS applications and subscriptions ....... [OK]
Checking for nginx ULIMIT value ..................................... [OK]
Checking for extra configurations in database not owned by any object [OK]
Checking the status of the required Apache modules .................. [OK]
Checking the configuration of Apache modules ........................ [OK]

Checking web server configuration

Reinstall SSL/TLS certificates and set the default certificate for
all IP addresses? [Y/n] y
Reinstalling SSL/TLS certificates ................................... [OK]
Applying the default SSL/TLS certificate to all IP addresses ........ [OK]

Repair web server configuration for all domains? [Y/n] y
Repairing web server configuration for all domains. This aspect
can be used with individual domains ("plesk repair web
example.com"), and on the server level ("plesk repair web") ..... [OK]

Repair server-wide configuration parameters for web servers? [Y/n] y
Repairing server-wide configuration parameters for web servers .. [OK]

Checking the usage of PHP handlers .................................. [OK]
Checking for obsolete PHP-FPM configuration files ................... [OK]

Error messages: 0; Warnings: 0; Errors resolved: 0

Should be OK! At least now.

But have a look at this:

[root@andreas ~]# netstat -tulpen | grep 8443
tcp6 0 0 :::8443 :::* LISTEN 0 539352 10181/httpd
Everything is running ok,and this before # plesk repair web ^^

Seems that sw-cp-server doesn't need port 8443.
Only Apache listens on ipv6 port 8443

 

[andreas.scherer]

Very interresing for me is that on my 2nd server apache behaves correct.

[root@lingua ~]# netstat -tulpen | grep 8443
tcp 0 0 0.0.0.0:8443 0.0.0.0:* LISTEN 0 26452 1198/sw-cp-server:
tcp6 0 0 :::8443 :::* LISTEN 0 26453 1198/sw-cp-server:

This server is not running under NAT. Maybe this is the problem here.

 

[andreas.scherer]

IP-Adressen​

IP-Adressen anzeigen, hinzufügen und entfernen

IP-Adresse hinzufügenIP neu lesenEntfernen
2 Elemente insgesamtEinträge pro Seite: 10 25 100 Alle

	IP-Adresse	Öffentliche IP-Adresse	Schnittstelle	IP-Typ	Websites
	172.17.145.125 /255.255.0.0	xxx.xxx.xxx.xxx	eno1	gemeinsam genutzt	2
	192.168.122.1 /255.255.255.0		virbr0	dediziert	0

Unfortunately, vmware is also installed on my problem server here. The problem may also be found here.
The public IP adress was made anonymous for security reasons.