Question How can I prevent the primary domain (hostname) from redirecting to the Plesk login?

[Rendor9]

Server operating system version

Ubuntu 24.04

Plesk version and microupdate number

18.0.71

Good day everyone! I installed Ubuntu 24 with Plesk Web Admin Edition, and I have the Plesk login pointing to the server hostname, let's say xxx.misite.com.
I notice that when I go to Make misite, your site - Make Misite, Your Site it redirects me to a Plesk promotional page, and when I go to Make misite, your site - Make Misite, Your Site (ssl) it sends me to the Plesk login.
How can I remove this last redirection (login) without creating a website for misite.com, since that would consume 1 of the 10 domains I have available? If they put a promotional page for HTTP, why not for HTTPS? Thanks!!

 

[Kaspar]

Via Tools & Settings > Customize Plesk URL change the option to "No custom URLs." This will limit access to the Plesk login page via port 8443 only.

 

[Dork]

Via Tools & Settings > Customize Plesk URL change the option to "No custom URLs." This will limit access to the Plesk login page via port 8443 only.

But in this case it will not be possible to get a certificate by Lets Encrypt

 

[scsa20]

But in this case it will not be possible to get a certificate by Lets Encrypt

It is still possible if you're using the hostname still and the hostname has an A record set up but honestly who really cares if it's going to be primary you that's using it? Just because it isn't secured with a valid certificate doesn't mean it's still being sent encrypted, you will just get a browser warning stating it's an invalid certificate and to be careful is all.

 

[trialotto]

But in this case it will not be possible to get a certificate by Lets Encrypt

@Dork

Yes, it is possible.

Just go to Tools & Settings > SSL/TLS certificates > button "+ Let's Encrypt" (click)

Afterwards, assign the LE certificate to Plesk and mail.

Before doing all of the above, make sure that

1 - the Custom URL is active,

2 - the DNS zone has been properly configured (and alive),

3 - you are logged in with the Custom URL (and otherwise, you might encounter issues).


I might have become stark raving mad, but it should still work like a charm - as it is intended.

Is there a reason why this LE certificate assignment did not work for you?!?


Kind regards....