• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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 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