• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Question Domain served outside of Plesk - how?

hello_world.c

New Pleskian
On a Linux server with Plesk Onyx I need to install a service that runs its own web server including SSL. I need to use the standard port 443. Can I add the domain for it in Plesk but tell Plesk not to handle it but forward it to the local service that handles it? If yes, how?
 
Theoretically (I haven't tried it myself), you can try the following scenario:

- create a docker container with your service with not 443 port
- create Plesk domain without hosting but with forwarding 443 port to port of docker container
 
Thanks for your replies. After much research I have found a different way. In recent versions of Plesk you can disable the nginx always reverse proxying the local Apache server and instead have it reverse proxy another local service. nginx handles the https protocol on port 443, you local server then runs unencrypted on a different port. This is described for example here:
The secret sauce is in the right nginx directives and the configuration of the other service that can't use hard redirects for example.
 
Back
Top