1. Please take a little time for this simple survey! Thank you for participating!
    Dismiss Notice
  2. Dear Pleskians, please read this carefully! New attachments and other rules Thank you!
    Dismiss Notice
  3. Dear Pleskians, I really hope that you will share your opinion in this Special topic for chatter about Plesk in the Clouds. Thank you!
    Dismiss Notice

SSL for domains on shared IP issue

Discussion in 'Plesk 9.x for Linux Issues, Fixes, How-To' started by BankHoliday, Feb 2, 2010.

  1. BankHoliday

    BankHoliday Guest

    Hello All,
    I have several domains running off the same IP.
    One of these domains has a page that I would like to SSL secure.
    If I enable SSL for this domain I can get the page to work under SSL but I get these errors in my log files:

    SSL server IP/port conflict: default-ip-ip-ip-ip:443 (/etc/httpd/conf.d/zz010_psa_httpd.conf:78) vs. sites.homedirectory:443 (/var/www/vhosts/sites.homedirectory/conf/httpd.include:12)

    Init: You should not use name-based virtual hosts in conjunction with SSL!!

    I have tried via plesk to craete a new self signed certificate and apply it to the domain but I cannot find any way to change the domain from using the default certificate that installed with Plesk to the self signed on i specifically created for the domain.

    Can anyone shine any light on this?
  2. BankHoliday

    BankHoliday Guest

    I suppose another thing I am wondering about is, since the messages are just warnings and the actual sites work as planned, acn I just ignore these warnings or does anyone know if that will cause some kind of snowballing issue in the background?
  3. Saif Bechan

    Saif Bechan Guest

  4. lvalics

    lvalics Silver Pleskian Plesk Guru

    Jun 20, 2003
    Likes Received:
    You cannot assign a self signed certificate to a domain until is not on a new IP, you need to have an exclusive IP to have his own SSL for it. Even then, if you will use self signed, you will get an alert that the site is not secure.

    We have an article about this, but still will not apply to a domain 100% OK, our article is more to avoid PLESK https:// error.