change plesk admin port 8443 Options

[BinaryFlux]

Hi i have been searching for a way to change the default plesk admin port from 8443 to 443.

The main purpose was to allow clients behind firewalls with strict rules to use the admin interface.

If you have ever tried to do this im sure you have found out that it is impossible to do since plesk has apache listen on 443 without binding to a specific ip.

I have a working solution and thought I would pass it along so that other plesk users can possibly benifit.

1. Create a new domain in plesk cp.yourdomain.com
2. create a vhost_ssl.conf file for this domain and add the following lines.

SSLProxyEngine on
ProxyRequests off
ProxyPass / https://servername.yourdomain.com:8443/
ProxyPassReverse / https://servername.yourdomain.com:8443/

3. Restart httpd

now when you goto https://cp.yourdomain.com you will see the plesk admin.

Basiclly when the request is recieved by the cp.yourdomain.com it will be proxied to the plesk admin by apache and it will appear to the user that the site is being served by cp.yourdomain.com

Note: You must use the server name as stated for this to work.


I hope this proves helpful to you.

Please be kind as this is my first post on this board.

Thanks

[y2krex]

Hey Guys,

when creating the vhost file it says you need to enter your servername. How can I find this out?

SSLProxyEngine on
ProxyRequests off
ProxyPass / https://servername.yourdomain.com:8443/
ProxyPassReverse / https://servername.yourdomain.com:8443/

Regards,

Jay

[dsoundmn]

that worked perfectly for me. thanks very much.

-dan horning

[nfviper]

Hi there,

I created a new domain called plesk.mydomain.com, bind a IP address in plesk on it and create a vhost_ssl.conf file under /home/httpd/vhosts/plesk.mydomain.com/conf with the following content:

CODE

SSLProxyEngine on

ProxyRequests off

ProxyPass / https://plesk.mydomain.com:8443/

ProxyPassReverse / https://plesk.mydomain.com:8443/

When I try to connect to https://plesk.mydomain.com I don't see the control panel. Any hints ???

Thx
Tom

[nibb]

I would also like this.
Could you be more spefific and publish a step by step guide?

I cannot make it work. And there are tons of users that need this too. Since most of use have client wich have firewalls and cant use the port 8443

[maxfalco]

Hey everyone, I figured this all out. Here is a step by step guide:

1) Create a new domain (not a subdomain) in Plesk called whatever.yourdomain.com where whatever=cp or plesk or whatever you want really, and yourdomain.com=a domain you have registered and pointing to the Plesk server.

2) Create a file called vhost_ssl.conf in the conf directory of the domain. Specifically: /home/httpd/vhosts/whatever.yourdomain.com/conf with this in it:

CODE

SSLProxyEngine on

ProxyRequests off

ProxyPass / https://servername.yourdomain.com:8443/

ProxyPassReverse / https://servername.yourdomain.com:8443/

where servername.yourdomain.com is the fully qualified host name (FQHN) of your server. For example, penguin.mydnshost.com.

3) Run this command:

CODE

/usr/local/psa/admin/sbin/websrvmng -v -a

4) Restart apache with this command:

CODE

service httpd restart

Now go to https://whatever.yourdomain.com (make sure you go to https and not http...http will just show a default Plesk placeholder page) and you should see a Plesk login screen.

Enjoy!

[TheUniverses]

Thats pretty cool. Though I don't quite trust apache's proxy module for its security.

[axxs]

There are problems with this setup in regard security, as it allows others to use the site as a proxy. This can be circumvented by adding a LocationMatch directive to your vhost_ssl.conf that denies every request that doesn't start with a slash for instance :

<LocationMatch "^[^/]">
Deny from all
</LocationMatch>

[madmac]

One final step, I've just figured out and done to 2 servers, both suddenly started working with no SSL validation errors .

1. Login to Plesk as admin
2. Click Servers > IP Addresses > (click the primary IP) > (select your own cert from the menu)

Apply and you're done Now visit https://yoursub.domain.com and there should be no warnings. Hit a bong.

This page is now the most complete resource for running Plesk under your own valid SSL certificate. Everyone else seems to miss something, like maxfalco's "Create a new domain (not a subdomain)" and run into problems. Between the latest comments by maxfalco, axxs and this one, you should have no issues at all. Enjoy!