SSL Init: SSL server IP/port conflict:

[UXMichael]

Hi,
i could not solve why the default domains block the dedicated domains with SSL

xxxxx IP conflicts vs default_xxxxxx


Thanks for your help

 

[UXMichael]

I think the included ip_vhosts_bootstrap.conf in the generated/xxxxx_server.include is too early.

SSL certifcates are going wrong in any browser because the default ips for 443 will be set after ip_vhosts_bootstrap.conf are included

But how the solution ?

 

[Stuff That Spins]

same problem

i'm having the same problem. it's causing apache2 to quit and not restart.

[Mon Nov 15 23:38:36 2010] [warn] Init: SSL server IP/port conflict: flightcrewcentral.com:443 (/var/www/vhosts/flightcrewcentral.com/conf/12898791460.00456300_httpd.include:10) vs. horde.webmail:443 (/opt/psa/admin/conf/generated/12898791910.32823200_horde.include:101)

thanks in advance to ANYONE helping out here.

 

[Stuff That Spins]

For the life of me, I can't seem to find anywhere to edit the domains SSL settings. I see this option in "Service Plans." In v 9.5.x you could edit the domain and configure their SSL settings. Help Parallels!

 

[Klan1 Network]

I had the same problem...

If you disable the WEBMAIL modules or uninstall it will "have a solution" I am researching more deeply to fix this :|

 

[Klan1 Network]

http://help.directadmin.com/item.php?id=226

[warn] Init: SSL server IP/port conflict: www.domain.com:443 Last Modified: Nov 20, 2008, 3:46 pm

If you get this warning in your apache logs, don't worry, it's perfectly normal.

[warn] RSA server certificate CommonName (CN) `localhost' does NOT match server name!?
[warn] Init: SSL server IP/port conflict: www.domain.com:443
[warn] Init: You should not use name-based virtual hosts in conjunction with SSL!!
The reason it's there is because DA uses name based hosting. What that means is you'll have many domains on one IP. The warning comes up because of the fact that only 1 ssl certificate is valid per IP address. An explanation on that can be found from the link below.

Note that these are just warnings, not errors.

On my server, my httpd process was shut down every ~20 minutes... using a lot of yum updates-remove and fixing some file permissions (my bad) all is good now