• The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Setting it up so secure CP access doesn't complain about the cert?

J

JerkyChew

Guest
I'm thinking this is a rudimentary question, but I can't find an answer anwhere.

When any of our clients try to access their control panel via https://domain.com:8443 , they are greeted by a secure cert mismatch message. Is there a way to set it up so they do not get this message? Maybe a self-signed cert or something?

Thanks in advance.
 
I have not done this myself (I make everyone use the hosting domain name URL), but you may want to search the forum for a recent post on 'shared SSL'
 
Originally posted by JerkyChew
I'm thinking this is a rudimentary question, but I can't find an answer anwhere.

When any of our clients try to access their control panel via https://domain.com:8443 , they are greeted by a secure cert mismatch message. Is there a way to set it up so they do not get this message? Maybe a self-signed cert or something?

Thanks in advance.

No, not in a shared hosting environment - you're only allowed to have one SSL certificate per IP adress (not a Plesk limit but more related to the way Apache works) - but maybe - as jamesyeeoc writes - it can be pulled off by faking some Shared SSL - but I don't know.
 
I do agree with Whistler that there should only be a single certificate per IP and that this is NOT a Plesk issue or limitation, and I would never do any workarounds on my own servers or any I manage.

But according to the following thread, they were able to do it.

http://forum.sw-soft.com/showthread.php?s=&threadid=27336

Advisory: I am not recommending you do this, nor am I condoning it. I am simply repeating information I happened to remember seeing elsewhere... I had no part in it, nor do I wish to :) Do so entirely at your own risk and any possible consequences are your own.

If it does not work, direct any questions to the original posters: cmurphy and mian
 
I'm having a similar problem.

I can't seem to get the server to use the proper cert when trying to go to https://servername.com:8443 I have the cert installed for that IP address and set as the default as well as installed on that hostname but it allways tells me the cert was assigned to plesk

Not sure where I'm missing this.
 
Back
Top