• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

[warn] Init: SSL server IP/port conflict

sao sang mo

New Pleskian
Hi,
I have a big problem with some stupid commands. Now, every time I restart httpd service, the error_log contains:
.....
[Fri Jul 13 02:13:37 2012] [info] Init: Initializing (virtual) servers for SSL
[Fri Jul 13 02:13:37 2012] [warn] RSA server certificate CommonName (CN) `plesk' does NOT match server name!?
[Fri Jul 13 02:13:37 2012] [warn] Init: SSL server IP/port conflict: client1.ext:443 (/var/www/vhosts/client1.ext/conf/httpd.include:13) vs. client1.ext:443 (/var/www/vhosts/client1.ext/conf/httpd.include:13)
[Fri Jul 13 02:13:37 2012] [warn] Init: SSL server IP/port conflict: client2.ext:443 (/var/www/vhosts/client2.ext/conf/httpd.include:13) vs. client2.ext:443 (/var/www/vhosts/client2.ext/conf/httpd.include:13)
[Fri Jul 13 02:13:37 2012] [warn] Init: SSL server IP/port conflict: client3.ext:443 (/var/www/vhosts/client3.ext/conf/httpd.include:13) vs. client3.ext:443 (/var/www/vhosts/client3.ext/conf/httpd.include:13)

[Fri Jul 13 02:13:37 2012] [warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
.....

I have googled the error, I may run some command to configuration each vhost run separate SSL certificate. But I dont want that, I only use only one shared SSL certificate. I also google to recofigure them but I have only found command in Plesk 10.x.

Hope you help me solve my problem.

many thanks
 
I think thats because several domains have been enabled for SSL and typically you have one domain, one cert per IP. You can ignore that error in that case.
 
Back
Top