• Plesk Uservoice will be deprecated by October. Moving forward, all product feature requests and improvement suggestions will be managed through our new platform Plesk Productboard.
    To continue sharing your ideas and feedback, please visit features.plesk.com

plesk panel default domain 8443

  1. B

    Resolved Cannot update SSL certificate used o port 8443 for plesk administration

    Dear all, I run Plesk on a single webserver with one domain and multiple subdomains. I secured all domains with Let's Encrpyt SSL certificates and all works fine. Also mail uses a new SSL certificate. I made sure that I go to "tools & settings" - "SSL/TSL Certificates", i issued a new...
  2. R

    Input I wrote a tutorial on how to redirect port 8443 to something more user friendly

    Hello, After spending a ton of time explaining to my customers why they need to accept an invalid certificate when accessing their Plesk Panel, or remember a long server-hostname-that-is-usually-gibberish.tld, I finally caved and spent a couple of hours searching for a solution. I wrote a...
  3. P

    Resolved Change FTPS certificate

    Hi. I have Plesk 17.0.17 on my Linux Centos 7.5 server and I have configured some domains on it. For one of this domains I am trying to use FTPS. But FTPS uses Plesk panel certificate and cause security error on FTP clients. Is is possible to provides domain's own certificate for FTPS? or is...
  4. T

    Resolved How to make Plesk available at only one domain?

    Hi, the default setting is that each of the hosted domains can be used to access the Plesk panel: domain1.tld:8443, domain2.tld:8443, ... And the chosen domain remains all the time in the address bar. But I can only use 1 valid ssl certificate for the Plesk domain - so I've chosen my...
Back
Top