• 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!
  • 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.

Plesk Update corrupts Nginx Config

TimReeves

Regular Pleskian
Twice it's happened - an automatic Plesk update has left Nginx non-functional, and my whole webserver thus effectively down. Thats bad.

At the start of August an Update deleted all the symbolic links in /etc/nginx/plesk.conf.d/vhosts. I had to regenerate them by turning "Process PHP by nginx" in "Web Server Settings" on and then off again. Another way would have been to manually create them (but I hate the syntax of "ln" for SymLinks).

At this point I should add that I'm using Plesk/Nginx in a rather special way. If one sets "Process PHP by nginx" to "On", then the Plesk Config contains a "location ~ \.php(/.*)?$ {" without any try_files, which means that attacks create a huge log from PHP-FPM, in which real problems get overseen. Further, a "location ~ /$ { index index.html ... }" which clobbers WordPress Permalinks. So I set "Process PHP by nginx" to "Off" but then pass PHP-Files to PHP-FPM in my own Nginx.conf, which I can now tailor to exactly how I need it. But still, that should not cause links or files to disappear during Plesk updates!

Then about 10 days ago, an Update simply deleted the Nginx Config file which I had registered under "Web Server Settings" / "Additional nginx directives" as "include "/var/www/vhosts/.../owncloud/owncloud.conf";". But only that one file - another domain on the host was not affected. What on earth can be going on?

Thanks for any help!
 
Back
Top