• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

plesk subdomain error

H

hispeedsurfer

Guest
Hi, I'am new to plesk. It's a great software.

I have to access the plesk control panel not on default port 8443, so I use now a subdomain configured with mod_proxy configuration

What I have tried:
Example
my domain: domain.org
created subdomain with plesk panel: plesk.domain.org with ssl, php and cgi support

in /var/www/vhost/domain.org/subdomains/plesk/conf/vhost.conf I use the following contents:
SSLProxyEngine on
ProxyRequests off
ProxyPass / https://domain.org:8443/
ProxyPassReverse / https://domain.org:8443/

After execution of /usr/local/psa/admin/sbin/websrvmng -u --vhost-name=domain.org and service httpd restart I call https://plesk.domain.org in my browser and I've been redireced to https://plesk.domain.org/login.php3?previous_page=index and this screen is a little bit diffrent to the default login screen. When try to access this page with my username root and password I receive a login error: Error: Login is incorrect.

If I use https://plesk.domain.org:8443 I've been redireced to https://plesk.domain.org:8443/vz/cp/panel/plesk/frameset and login is no problem.

Can someone explain me what I have to do using plesk without port statement.

Thanks
 
Hi breun,

thank you for your reply.
I don't want to change the internal plesk port, I want use a subdomain (443) to proxy via apache to the default (httsp://domain.org:8334) as I described above.

But the approach I found here in forum and in the internet (http://alexle.net/archives/152), doesn't work for me.
 
Hi,

is somewhere out anyone have running Plesk 8.6 via proxy/subdomain and can explain me what I have to install/download/configure/todo get this working? Help would be appreciated.
 
Hi,

No configuration problem.

In the past I used root as username on login screen (https://domain.org:8443/)

Access with subdomain (in my case https://plesk.domain.org/) the root login name is unkonwn. Accidentally I found out to use admin as username. Why? I don't know! Main thing - is working now.

Thanks
 
The Plesk administrator's account has been 'admin' for as long as I can remember, not 'root'.
 
Back
Top