• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1556
  • Last Modified:

[warn] Init: SSL server IP/port conflict:

Hi,

I have an VPS account with a2hosting and I'm getting this SSL error in my Apache error logs. I believe this is stopping my curl_exec() from being able to connect properly. How can I resolve this error message?

Thanks,
waffe


[warn] Init: SSL server IP/port conflict: elggtest.my1.com:443 (/home/httpd/elggtest.my1.com/conf/kloxo.elggtest.my1.com:71) vs. elggtest2.my1.com:443 (/home/httpd/elggtest2.my1.com/conf/kloxo.elggtest2.my1.com:71)
[Fri Apr 09 03:36:36 2010] [warn] Init: SSL server IP/port conflict: my1.com:443 (/home/httpd/my1.com/conf/kloxo.my1.com:69) vs. elggtest2.my1.com:443 (/home/httpd/elggtest2.my1.com/conf/kloxo.elggtest2.my1.com:71)

Open in new window

0
waffe
Asked:
waffe
2 Solutions
 
Steve BinkCommented:
Are you trying to use more than a single certificate on that IP?
0
 
arnoldCommented:
Routinet pointed out that your configuration files for:
/home/httpd/elggtest.my1.com/conf/kloxo.elggtest.my1.com:71) vs. elggtest2.my1.com:443 (/home/httpd/elggtest2.my1.com/conf/kloxo.elggtest2.my1.com:71)
[Fri Apr 09 03:36:36 2010] [warn] Init: SSL server IP/port conflict: my1.com:443 (/home/httpd/my1.com/conf/kloxo.my1.com:69)

Use the same IP/Port.

While you can host multiple web sites on the same IP, SSL binds to the IP/port and does not provide/use host headers as a means to differentiate. Since the Secure connection to the server has to be established first and then the request is sent, there is no way the server can know ahead of time which certificate and thereby encryption to present to the client browser.
0
 
waffeAuthor Commented:
I removed my two sub-domains and the errors went away but my curl issue still persists!

Thanks,
waffe  
0

Featured Post

Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now