• 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 NGINX, PLESK multiple HTTPS domains, single .conf

Dezzle

New Pleskian
Hey Pleskian's

I'm not totally proficient with the use of PLESK so very much consider myself a newbie however currently running a new VPS of which the PLESK "Web Admin Pro" package allows up to 30 domains. Although the web panels are very easy to utilise of which I'm very happy with I'd like to combine a set number of domain names (each of which are https based) in to a single NGINX .conf file like a server block, example below.

NGINX:
server {
    listen *:443 ssl;
    server_name domain1.com www.domain1.com;
    ssl_certificate /path/to/domain1.crt;
    ssl_certificate_key /path/to/domain1.key;
    return 301 https://www.domain1.com$request_uri;
    }
server {
    listen *:443 ssl;
    server_name domain2.co.uk www.domain2.co.uk;
    ssl_certificate /path/to/domain2.crt;
    ssl_certificate_key /path/to/domain2.key;
    return 301 https://www.domain2.co.uk$request_uri;
    }
server {
    listen *:443 ssl;
    server_name domain3.eu www.domain3.eu;
    ssl_certificate /path/to/domain3.crt;
    ssl_certificate_key /path/to/domain3.key;
    return 301 https://www.domain3.eu$request_uri;
    }

However I've not fully managed to get this working at present but the notion works absolutely fine if I create a new domain within PLESK, assign said domain to the same directory. But as a user, subscriber I'm utilising one of my possible 'up to 30' domains' within the package and have three or more times the configuration files, I'm seeking here to both minimise and streamline but also feel as if I could be invalidating some PLESK small print or that possibly this is a viable option but some configuration I have completed so far is incorrect.

Does any other user utilise an outcome like what I've mentioned?

-The easiest solution here is to upgrade to a PLESK unlimited package but I am hoping to keep it all nimble, minimal and fairly efficient as I rise through the package options rather then just assigning however many domain names to PLESK and allowing it along with other software packages it relies on to sort everything out.

Thanks for allowing me to become a member on the PLESK forum, I really enjoy using PLESK for its ease and web panels too. It's lovely to use on an everyday basis and grow with.

Kind regards,
 
Back
Top