- Server operating system version
- Debian 10.13
- Plesk version and microupdate number
- 18.0.57 #5
Hello everyone,
Our company manages around 70 Plesk Obidian servers for various customers. For the past few days we're starting to see some errors involving the modifications of Apache web server config. Updating the Apache web server config generates the following error:
These systems are Debian 10, which has it's Apache config in /etc/apache2/ so there is no /etc/httpd/. This has never been an issue in the past and Plesk has always just managed the configuration in /etc/apache2/ where it belongs. bug ID PPPM-11215 doesn't appear to be applicable here since nginx isn't being used.
Running a 'plesk repair web' just generates more of the error messages as seen above and doesn't manage to fix anything.
Anyone has any idea what's going on here?
Our company manages around 70 Plesk Obidian servers for various customers. For the past few days we're starting to see some errors involving the modifications of Apache web server config. Updating the Apache web server config generates the following error:
New configuration files for the Apache web server were not created due to the errors in configuration templates: mkdir: cannot create directory ‘/etc/httpd/conf/plesk.conf.d/webmails’: No such file or directorymktemp: failed to create file via template ‘/etc/httpd/conf/plesk.conf.d/webmails/<website-name>_webmail.conf.XXXXXX’: No such file or directoryCan not create temporary file. Detailed error descriptions were sent to you by email. Please resolve the issues and click here to generate broken configuration files once again or here to generate all configuration files. See the details in Configuration Troubleshooter
These systems are Debian 10, which has it's Apache config in /etc/apache2/ so there is no /etc/httpd/. This has never been an issue in the past and Plesk has always just managed the configuration in /etc/apache2/ where it belongs. bug ID PPPM-11215 doesn't appear to be applicable here since nginx isn't being used.
Running a 'plesk repair web' just generates more of the error messages as seen above and doesn't manage to fix anything.
Anyone has any idea what's going on here?