Lars Lehmann
New Pleskian
We use nginx as a reverse proxy for directing the traffic of a subdomain to a specific port (11111 for example).
We can set this up in the nginx.conf file in the subdomains system config.
But always, when the subdomain is updated over plesk (when applying a new ssl certficate for instance), this conf file is overwritten and our custom configuration is lost. After this, our webapp is not accessible anymore and we need to change the file again.
My Question:
is it possible to make the following configuration or a similar permanent? (we also tried the Additional nginx directives, which doesn't work).
```
location / {
proxy_pass https://93.90.178.92:11111;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;
}
```
We can set this up in the nginx.conf file in the subdomains system config.
But always, when the subdomain is updated over plesk (when applying a new ssl certficate for instance), this conf file is overwritten and our custom configuration is lost. After this, our webapp is not accessible anymore and we need to change the file again.
My Question:
is it possible to make the following configuration or a similar permanent? (we also tried the Additional nginx directives, which doesn't work).
```
location / {
proxy_pass https://93.90.178.92:11111;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Accel-Internal /internal-nginx-static-location;
access_log off;
}
```