The operating system my web server runs on is (include version):
ubuntu 20.04 (x64 raspberry pi 4)
I can login to a root shell on my machine (yes or no, or I don’t know):
yes
Hi,
Not sure if anyone can help…
I’ve noticed that after a reboot if I check the status of nginx i get the error nginx: [warn] “ssl_stapling” ignored, host not found in OCSP responder “ocsp.int-x3.letsencrypt.org” in the certificate…"
I have the resolver IP address set, and the ssl_trusted_certificate set to chain.pem in my domains live folder of lets encrypt.
If I restart nginx and check the status it starts with no errors.
Does anyone have any ideas? (I’m far from an expert )
Thanks in advance.
I have the IPs set to my local DNS (another pi4) and my ISPs as backup. I’ve tried 8.8.8.8 too. Was set to itself 127.0.0.1 originally, which also works but not after a reboot.
I’d not tried the dig you suggested but have now and it gives an answer.
I’ll check you last link about starting after networking; I’m very new to all this, 6 months linux/pi - I’ll see what i can find out
I assume the “After=syslog.target network-online.target remote-fs.target nss-lookup.target” is the part instructing nginx to start after networking…
i ran:
cat /lib/systemd/system/nginx.service | grep After
and got the output:
After=network-online.target remote-fs.target nss-lookup.target
I guess this is instructing the same thing?
The only thing i haven’t tried is to extend the resolver timeout more? I have 10s set at the moment.
Thanks for the reply.
I’ve removed the timeout and it still throws the error after a reboot.
nginx still starts and I dont often reboot and very rarely get a power cut to force one so i may have to live with it.
Seems to be a pi problem (or maybe my router?) rather than ubuntu/nginx. I’ve just tired my other pi running nginx 1.14.2 on raspberry os and it does the same.
I think this is a bug in nginx and/or your default systemd configuration but it’s possible that people on this forum don’t have the right expertise to diagnose it, unfortunately. You might be able to get more ideas from a different forum.
A workaround without solving the problem might be to create another startup task, or recurring task, to restart nginx once soon after each reboot.
Thanks for the reply.
I went with your work around idea - set a cron job to run as root seemed the easiest: @reboot sleep 30 && sudo service nginx restart
This works fine.
Without the time delay it doesn’t work. You could most probably get away with less time, I’ve not tried .