• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • 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.

:8443

  1. 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...
    • Razva
    • Thread
    • 8443 :8443 plesk panel default domain 8443 without_8443
    • Replies: 2
    • Forum: Open Topics
  2. C

    Question Avoid use ip address to log into plesk ?

    I set the url of Plesk with let’s Encrypt and using mydomain:8443 everything is ok, but if I use the ip address:8443 the connection is not trusty. There’s a way to avoid the possibility to make the login using the server ip address? Thanks
Back
Top