Acces Plesk through subdamain

[emperor]

Is it possible to make access to the Plesk panel, through a subdomain ?

instance: domain.com:8443 (NO)
panel.domain.com:8443 (NO)
panel.domain.com (YES)

 

[caomhan]

I don't know if it is possible to run Plesk Panel or port 80. Your Apache webserver is using this port. Plesk Panel has it own Webserver which is running at 8443 by default. Its not possible to bind two webserver on the Same Port i think.

Whats about a simple Redirect?

 

[gbotica]

Hi, Yes, you can run Plesk under a subdomain. However, as @caomhan has pointed out, you can't use port 80, so your second option is your best choice.

https://panel.domain.com:8443

 

[emperor]

How to do the following?
httpS://panel.domain.com:443/

Such a scenario is possible, and whether it is the right decision?

 

[trialotto]

@emperor,

The port 8443 is obligatory in Plesk installations, it is the default port.

It is not adviceable to change that port, by the way.

In order to have https://panel.domain.com:8443, you have to follow these steps:

a) access DNS management for the domain.com, with this DNS management often available at the registrar at which you registered domain.com, (and)

b) create an A record, pointing to the IP assigned to your server (that runs the Plesk instance), (and)

c) wait a bit for DNS propagation.....and you are ready to access the panel via https://panel.domain.com:8443 (and that is all!)

Note that there are other ways of achieving the above, but this is the most convenient method: you do not have to mess with hostnames, CNAME or PTR records etc. etc.

Hope this helps!

Regards....

 

[emperor]

On my server, one address IP and multiple domains.
I can get into the panel through any domain:
domain.com:8443/
domain-2.com:8443/
my.domain.com:8443/
my.domain-2.com:8443/

How can I solve this?

 

[trialotto]

@emperor

This

I can get into the panel through any domain:
domain.com:8443/
domain-2.com:8443/
my.domain.com:8443/
my.domain-2.com:8443/

is default behaviour.

In essence, any domain pointing to the IP of your server will end up at the Plesk Panel, due to the addition of port 8443 (i.e. Plesk "listens" on port 8443).

However, that does not imply that it is impossible to "change" default behaviour: one can change Nginx directives, but all that work would not be worthwhile.

I would strongly advice to leave it this way.

Regards....

 

[emperor]

Thank you all very much for the clarification.
Topic can be closed)

 

[LytraX]

I don't know if there was this setting to do this back then when this was asked, but nowadays this is built-in inside Plesk.

1. Create a subdomain that you want to use to access Plesk panel (i.e. my.server.com)
2. Secure it with an SSL certificate
3. Go to "Tools & Settings" > "General Settings" > "Customize Plesk URL", select the second option "The specified domain or subdomain that resolves to the server IP address but is not used for hosting" , give your full subdomain my.server.com and save