Question Plesk Onyx & nginx: How to define separate settings for HTTP and HTTPS

[B_P]

Hi all,

while switching to a new system (Ubuntu 12.04 ->16.04) and Plesk Onyx (from 12.5), I see that nginx was enabled automatically. Since this seems to be an interesting combination, I started experimenting...

Now the first question that I have: For Apache, I can define for each website/subdomain custom settings for Apache & nginx. For Apache, these can be different for HTTP and HTTPS. However, for nginx there is only one field. How can I define different settings for HTTP and HTTPS?

- This is for instance necessary for HTTP to HTTPS redirects (where the redirect is only required on the HTTP port). Here separate configuration settings would be helpful to prevent the execution of additional regular expressions and if statements...

 

[UFHH01]

Hi B_P,

This is for instance necessary for HTTP to HTTPS redirects

surprise, surprise... Plesk may solve this for you: => HOME > Domains > (sub)domain > Hosting Settings >

​

 

[B_P]

Hi B_P,
surprise, surprise... Plesk may solve this for you: => HOME > Domains > (sub)domain > Hosting Settings >

View attachment 12295 ​

Well, I have a special case which I use to facilitate accessing the plesk panel:
- The Plesk panel is located at https://plesk.domain.tld:8443/ and is expected to use a Let's encrypt certificate
- The server also hosts domain.tld
- Any access to plesk.domain.com (HTTP, HTTPS on regular ports) should be redirected to the Plesk URL
- ... except those which are required for the validation of the Let's encrypt certificates (/.well-known/acme-challenge/.*)

To simplify the access, I created a subdomain plesk.domain.tld. Now the idea is the following (works with Apache and Plesk 12.5):
a) When accessing http://plesk.domain.tld/ (or any location on this subdomain except those for Let's encrypt), I get redirected to http://plesk.domain.tld/:
RedirectMatch 301 ^(?!/\.well-known/acme-challenge/).* https://plesk.domain.tld$0 (additional HTTP directives used with Plesk 12.5)
b) When accessing https://plesk.domain.tld (or any location on this subdomain), I get redirected to https://plesk.domain.tld:8443/
Redirect permanent / https://plesk.domain.tld:8443/ (additional HTTPS directives used with Plesk 12.5)

How would this work with nginx?

In addition, I assume that there are other cases where different settings may be required for HTTP and HTTPS...

 

[B_P]

Btw: using the "standard forwarding" hosting type is not allowed (from plesk.domain.tld to https://plesk.domain.tld:8443/) since the interfaces complains that it is the same address (ignoring the ports...).

 

[UFHH01]

Hi B_P,

am I correct, that you opened the thread, because of Let's Encrypt and the desire to secure the server - hostname with a Let's Encrypt certificate? Well good news... pls. visit: => #5


If you desire to redirect visitors from any URL ( of your hosted domains on your server ) with the port specification ":8443" to an URL of your choice ( i.e. https://plesk.YOUR-DOMAIN.COM:8443 ), you would follow:

=> How to change Plesk redirect URL ( Plesk KB - article 115000068605 )​

Could you pls. post the corresponding log from Let's Encrypt, if you experience any issues, when trying to create a certificate for your (sub)domain? You should NOT need any apache ( or nginx ) rewrites, when you use the Plesk - Let's Encrypt - Extension.