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

Port 8443 SSL Certificate (again)

Discussion in 'Plesk for Linux - 8.x and Older' started by Strikefinder, Apr 9, 2006.

  1. Strikefinder

    Strikefinder Guest

    Hey folks,

    I've started running Plesk 7.5.3 recently on a VPS and am trying to utilize a SSL certificate I've purchased to secure the login to my control panel for my clients.

    I've successfully installed and verified the certificate for the server and the associated domain name. If I utilize the certificate to reach content in the /httpsdocs directory of the associated domain, I receive the proper certificate and no "The name on the certificate is invalid..". However, when accessing port 8443, I get a warning in every browser I've tried.

    I have completely configured the certificate in Plesk on the server page and made it the 'default' certificate and marked it and checked the 'setup' button, at which point the server says that it is reloading the SSL certificate, waits a few moments, then returns me to my CP. I then close all browser windows and try again, but this doesn't work. It always tells me upon accessing port 8443 that the certificate is signed by "localhost.localdomain". I even deleted the default certificate (after backing it up), and it still says the same thing.

    I did a search on the issue and have come up with a few dozen posts about the issue, and have spent the better part of today trying all the ones that I could find. I have edited the httpsd.conf and httpsd.conf.def files with multiple restarts of Plesk, Apache, and the entire server. Nothing seems to work.

    Please, folks, I'm stumped on this one. I don't want my clients to be logging in and seeing warnings that the site is insecure, or even possibly insecure, and I don't see why they should have to. Please, please help me find a way to get this fixed.
  2. slaphost

    slaphost Guest

    I am having the exact same problem. I hope someone will be able to help out.

    Were you able to figure it out?
  3. Strikefinder

    Strikefinder Guest

    I've learned that accounts running through Virtuozzo will always remap a generic certificate over port 8443, no matter how you set up your account.

    I ended up streaming the date through a vhost_ssl.conf file located in the conf directory of the domain I wanted to connect through:

    ServerAlias admin.servername.com
    SSLProxyEngine on
    ProxyRequests off
    ProxyPass / https://admin.servername.com:8443/
    ProxyPassReverse / https://admin.servername.com:8443/

    After uploading this file, I reconfigured this entry in the web server and restarted the web server, and it now streams the whole connection over port 443 without the requirement for the port designation.

    The problem remains that the phpMyAdmin utility that comes up with the button goes back to port 8443 and requires that I re-login, but I'm working on that, as well.

    Hope that helps!