How to secure a Plesk hostname on port 8443 with an SSL certificate (Let's Encrypt / other certificate authorities)

Follow

Comments

37 comments

  • Avatar
    Tony Hager

    I followed the instructions and got the Lets Encrypt to install and it works.

    How can you create a redirect now so when you type server.example.com into the browser it sends it to the https://server.example.com automatically?

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello Tony Hager

    This instruction should help: https://support.plesk.com/hc/en-us/articles/115000327829

    0
    Comment actions Permalink
  • Avatar
    b_p

    If you try to use a custom URL/domain to access the panel (https://docs.plesk.com/en-US/obsidian/deployment-guide/plesk-installation-and-upgrade-on-single-server/customizing-plesk-url.76455/), how do we need to set up Plesk so that the proper SSL certificate is provided? Right now, the general server name is server.example.com (which is used for mail access and panel access via https://server.example.com:8443), while I tried to set up a different subdomain (sub.anotherdomain.com) as Plesk URL.

    If you do so, the server does not deliver the right certificate when trying to access https://sub.anotherdomain.com, no matter whether I set the hosting type of sub.anotherdomain (in one of the subscriptions) to webhosting or no hosting.

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello b_p

    To be on the same page, please let me know whether the certificate for sub.anotherdomain.com is selected at Tools & Settings > SSL/TLS Certificates > Certificate for securing Plesk? If not, please, select it.

    0
    Comment actions Permalink
  • Avatar
    b_p (Edited )

    Hi Ivan Postnikov my idea was that

    a) the server remains accessible at https://server.example.com:8443 (this is the address all existing clients know and use and this is also the smtp host name for all incoming mails) and

    b) will additionally be accessible at https://sub.anotherdomain.com (for new clients or those who update their bookmarks)

    Given that the "normal" nginx (hosting all other sites and sub.anotherdomain.com) is used as well as the sw-cp-panel nginx (for direct access to port 8443, I'd assume that this should be possible except for having to choose two different certificates.

    0
    Comment actions Permalink
  • Avatar
    Lisa Bond

    Can someone help pls I have port 8443 secured however I'm unable to secure open port 9001 which I need for my app to work can you please link me or provide solution how to ssl custom port 9001 please? Thank you

    0
    Comment actions Permalink
  • Avatar
    Ivan Postnikov

    Hello 

    b_p

    I see what you mean now. Yes, I believe that should be possible from a technical perspective. Feel free to submit a feature suggestion here.

    Lisa Bond

    Plesk doesn't support this custom scenario. Your App may be secured manually only.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Have more questions? Submit a request