• The APS Catalog has been deprecated and removed from all Plesk Obsidian versions.
    Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
  • Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.

Resolved Plesk Login for Customers over Subdomain with Certificate.

cpulove

New Pleskian
Hi, I'd like to know, what the best practice would be, to create a custom login for Plesk Customers over their own URL.

So lets the Plesk Sever Login is plesk.hostname.xy:8443 and it is secured via letsencrypt with the certificate for the Plesk Server: plesk.hostname.xy

How can I setup a Plesk Login with certificate with the customers Domainname? >> plesk.domainname.xy:8443

A DNS A or CNAME Record so far brings up the loginpage, but as expected, without proper SSL, as the port shows to the Plesk Servers hostname with the certificate from there >> plesk.hostname.xy.

Any help would be nice!
 
One way to achieve this, at least in Obsidian (did not test it in onyx) is this way:

  1. Add a subdomain under each customer. I will use here plesk.customer.com as example.
  2. Go to plesk.customer.com > Dashboard > PHP
  3. Uncheck the PHP Support option
  4. Press OK
  5. Go to Domains > plesk.customer.com > Hosting & DNS > Apache & nginx Settings.
  6. Uncheck the Proxy mode option.
  7. Press Apply
  8. Add the following lines into Additional nginx directives:
    Code:
    location / {    proxy_set_header X-Forwarded-For $remote_addr;
        proxy_set_header Host $http_host;
        proxy_pass https://127.0.0.1:8443;
    }
  9. Press OK
As you can see here, both will have a valid SSL and open the panel:
1744278837371.png
 
Sorry for my late reply! I integrated it today and indeed, this works flawless.
So thx a lot! Appreciated this...
 
Back
Top