Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
It produced this output:
nginx: [warn] "ssl_stapling" ignored, no OCSP responder URL in the certificate "/usr/local/etc/letsencrypt/live/truenas/fullchain.pem"
nginx: [warn] "ssl_stapling" ignored, no OCSP responder URL in the certificate "
My web server is (include version): nginx v 1.20.1
The operating system my web server runs on is (include version):TrueNAS-12.0-U5.1
My hosting provider, if applicable, is: self
I can login to a root shell on my machine (yes or no, or I don't know):yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):1.18.0
Do you mean log error file? I have a feeling this whole mess is because of nginx version 1.20.1 and I read somewhere that OCSP is supported in =>1.3.7 error.log.txt (196.4 KB)
hmm...
IT seems that, in your case, since it is using the default trusted path chain which ends with "DST Root CA X3 (expired)", nginx fails to find the relevant OSCP information needed.
see:
I would try removing the last cert from the fullchain.pem file and restart nginx.
If that workaround fixes the problem, you will have to switch to using the alternate trust path chain.
If it does NOT fix the problem, please show the nginx vhost config file that serves that FQDN securely.
I don't think it has to do with that, as nginx usually only cares about OCSP info for the leaf. To me it looks like some weirdness is going on with the nginx config itself.
I see that you've commented out some lines. Can you uncomment them, but leave this specific directive commented? Don't forget to reload/restart nginx after making changes.
When you comment out those lines, then nginx may default to using whatever is in the main config.
Let's have a look at that file too.
maybe: /etc/nginx/nginx.conf