• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    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.

Issue Debian 10 Nginx fails to start - missing ssl_stapling resolver

TimReeves

Regular Pleskian
I set up a new BareMetal server with Debian 10 and Plesk 18.0.28. Initially all was well - but the more Domains I migrated the slower Nginx restarted. Finally, the start of Nginx timed out. Initially I thought this may have to do with the last domain migrated (Nextcloud with 90GB data). But it turned out to be something else:
  • I do NOT have bind running, as all my domains are managed elsewhere
  • /usr/sbin/nginx -t was timing out, so Nginx could not be (re)started
  • For each configured domain (judging by the number of messages):
    nginx: [warn] "ssl_stapling" ignored, host not found in OCSP responder "ocsp.int-x3.letsencrypt.org" in the certificate "/opt/psa/var/certificates/scfEGoDfp"
After the searching the net I found a hint for the solution: I added an own "nginx-ssl-stapling.conf" to /etc/nginx/conf.d, which contains:
ssl_stapling on;
ssl_stapling_verify on;
resolver 8.8.8.8 8.8.4.4 valid=300s;
resolver_timeout 15s;


Now, the resolver is specified and Nginx starts very fast, as expected, no errors.

Please, check this out and provide an appropriate patch to save a lot of grey hairs on administrator heads :)

BTW the sw-cp-server instance of Nginx does not seem to have this problem.

Cheers, Tim

P.S. In general modern Plesk is for me a fantastic tool, saves me sooo much time.
 
Back
Top