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. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: sensi.com.au
I ran this command:
Starting NGINX service or using test:
My web server is (include version):
nginx version: nginx/1.18.0 (Ubuntu)
The operating system my web server runs on is (include version):
I can login to a root shell on my machine (yes or no, or I don't know): Yes
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot 1.21.0
The actual certificate file is in /etc/letsencrypt/archive and the permissions are fine. The symlink to the actual fullchain.pem is also fine and I can read the file without problems and there are no obvious issues.
This system has been working for some time, it stopped when adding some additional sites to NGINX config.
The other sites which also use Letsencrypt certificates are working. It's only this one (which is a wildcard certificate, BTW, in case this matters) that is not able to be loaded by NGINX.
I have gone through everything. Does anyone know how to get more detailed debug info from NGINX or some OpenSSL command that would help get to the bottom of the issue?