• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Problems of Web-mail and Web-server

synthetic5995

Basic Pleskian
Hi,

I've some problems with web-mail and web-server. When i add new Subscription with Web-hosting Service. It show error:

"New files of configuration for Apache web server were not built due to errors in configuration templates: nginx: [emerg] open() "/var/run/nginx.pid" failed (13: Permission denied) nginx: configuration file /etc/nginx/nginx.conf test failed . The detailed error message was e-mailed to you, so please check the e-mail, fix the errors, and click here to retry generating broken configuration or click here to retry generating of all configurations."

"Error: New web server configuration for some of the subscription's domains was not built due to errors in configuration templates. The detailed error message was e-mailed to you, so please check the e-mail, fix the errors, and click here to retry generating configuration."

And in the email:

"Unable to generate the web server configuration file on the host <shared04.gdsvn.net> because of the following errors:

nginx: [emerg] open() "/var/run/nginx.pid" failed (13: Permission denied)
nginx: configuration file /etc/nginx/nginx.conf test failed


Please resolve the errors in web server configuration templates and generate the file again."

But web-mail (horde) and web-server working fine. What's the problems?

Thank You So Much!
 
Since you (as many others) didn't specify Plesk and OS version, I'll just shoot blindly here. If you have SELinux, disable (set to permissive mode) it. If this helps, check that you have correct policies installed and post related errors from audit.log.
 
Back
Top