8443

Hi everyone, brothers, sisters, gurus, masters and sifus... I've searched for solution since a few days ago but found nothing so I had to register acc to start posting. Here's some question and answer (that I found with reading + trial and error while writing this post). 1. (Question)...

i Can't access panel with domain or ip, after i added ssl on my subdomain in another panel. I have tried all the existing guides but to no avail. please helpme

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...

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...

When a customer has a problem with a website, we normally would go to customerdomain.com:2222 (2222 because of directadmin) and it would redirect us to the serverhostname:2222. This way we could quickly find out on which server the customer website is located. And we would be on the login page...

Hey Guys I recently ran into some issues, when my customers tried to access their Plesk, they always got a Page wich says: Not Secured page (because my servers Certificate is made for the servername:8443) Can i use different Certificates to provide a secure connection with all pages :8443...

Hi, all of a sudden I am not able to reach the cp both on https://serverurl:8443 and http://serverurl:8880. Website and other services seem to work as usual though. Now, since I know that this can be related to a variety of issues, I would appreciate very much if someone could help me in...

I'm kind of shocked no one has requested or written a guide on making the Plesk Login to only allow login in from a single URL, not the VhostDomain.com:8443 which produces an insecure SSL warning. Is there a trick to making all domains server wide forward to...