• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be 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.

Question Redirect customerdomain.com:8443 to serverhostname:8443

LarsK

New Pleskian
When a customer has a problem with a website, we normally would go to customerdomain.com:2222 (2222 because of directadmin) and it would redirect us to the serverhostname:2222. This way we could quickly find out on which server the customer website is located. And we would be on the login page of that server. When I try this on our new Plesk servers I get the plesk login page under the users domain name (customerdomain.com:8443) with SSL cert error, so no redirect to the server hostname.

I found the following support page:

I would have to add:

if ($host !~ 'hostname.com'){
rewrite ^/(.*)$ https://hostname.com:8443/$1 permanent;
}

To /etc/sw-cp-server/conf.d/z-plesk.inc. But wouldn't this also redirect customerdomain.com to serverhostname:8443, not only customerdomain.com:8443?
 
Back
Top