Resolved best-practice rewrite hostname-domain to plesk login

[FYI]

Server operating system version

Ubuntu 22.04

Plesk version and microupdate number

18.0.50

Hey guys,

i've setup the plesk server on hostname p1.domain.tld and the login is available on p1.domain.tld:8443 by default. I'm using 2 slave servers with DNS Slave Manager as authoritive dns servers. To be able to do that, i created the domain, which i just uses for hostnames, as a domain and edited the dns zone so its works as dns authoritive zone.

What happens?
When someone gets to domain.tld or p1.domain.tld he sees a plesk default page.

Question:

1. Whats the smartest solution to redirect domain.tld and p1.domain.tld to p1.domain.tld:8443?
2. Is there a solution to get the login to p1.domain.tld and only rewrite domain.tld to p1.domain.tld (so entering a port isnt needed anymore)
3. Whats the "best-practice" on that?

 

[Peter Debik]

Would customizing the Plesk login URL help in this case?

https://support.plesk.com/hc/en-us/articles/213945625-How-to-customize-Plesk-URL

 

[FYI]

It would, but can i overwrite in this case a existing domain?

 

[scsa20]

As long as your A records for p1 and p2 is pointing to the correct IP addresses of where you'd want it to go, then plesk login URL will work just fine and direct you wherever. I wouldn't recommend making a subdomain in the panel of p1 and p2 though, cause that could cause problems, just make the A records.

 

[FYI]

Okay sounds good. Thanks - its solved.

 

[FYI]

Ah damn, still a question open.

I added the A/AAAA Record and then changed the plesk url to it (p1.domain.tld which is also the hostname.

There is a LE Cert added with correct domain in it - but chrome shows insecure connection.

I tested from different devices in different networks and with devices that had no cache on these domain/ip but everything the same.

But when i do ssl check with ssllabs everything is fine...

 

[scsa20]

That's going to be normal since your panel is probably still using the old certificate. You would just need to log in and tell it to reissue the certificate for the correct domain. Refer to the following article to give you some guidance:

Securing Plesk and the Mail Server With SSL/TLS Certificates

This topic explains how to manually secure both Plesk and the Plesk mail server with the following certificates’ type...

docs.plesk.com

 

[FYI]

Ahhh...no its not a old certificate...i got it...Its Not forwarding from HTTP to HTTPS

But at the Plesk Login URL i just can enter RFC conform domain name.

Hmmm...If its not a added domain, i would say i need to set rewrite within a vhost configuration manually for that custom plesk login domain?

 

[FYI]

https://support.plesk.com/hc/en-us/articles/213945625-How-to-customize-Plesk-URL

It says that if you want to use an existing domain that is set up, you absolutely have to enable 301 SSL forwarding there.



But if you take a domain that is not set up as your own domain, as you recommended, you have no "standard" way to set up an HTTPs rewrite.

 

[FYI]

https://support.plesk.com/hc/en-us/articles/360015823179-Why-there-is-no-redirect-from-http-to-https-to-access-Plesk-login-page-

Got it