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

Issue Error after Letsencypt certificate update

onki

Regular Pleskian
Hi,

I got a webserver error by mail and all my websites were down:


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

Template_Exception: AH00526: Syntax error on line 109 of /etc/apache2/plesk.conf.d/server.conf:

SSLCertificateFile: file '/opt/psa/var/certificates/cert-QmL4bE' does not exist or is empty

file: /opt/psa/admin/plib/Template/Writer/Webserver/Abstract.php

line: 75

code: 0


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

At the same time I got the info that a Letsencrypt certificate was renewed. After clicking on rebuild all configuration files it all worked again. Is there something I can do to prevent that problem?

Best regards
Onki
 
OK - this seems to be identical with my problem.
We'll see if this will be fixed in the next update.

Best regards
Onki
 
Is there something I can do to prevent that problem?
No. It is a timing issue / race condition. Certain operations are sometimes performed before others, so that unfortunately it is still possible that the certificate filename entry in the web server configuration is pointing to a non-existing certificate.
 
Back
Top