Cannot load certificate "/etc/letsencrypt/live/

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. |, so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command: Nginx -t
{more information - I created a subdomain and acquired certificate using certbot [sudo certbot --nginx --hsts --staple-ocsp --must-staple -d]. However, at some point, i decided to pull down the subdomain and redo it again and i therefore removed the certificate and the subdomain server block and folder. Now Nginx configuration has an error}.

It produced this output:nginx: [emerg] cannot load certificate "/etc/letsencrypt/live/": BIO_new_file() failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen('/etc/letsencrypt/live/','r') error:2006D080:BIO routines:BIO_new_file:no such file)
nginx: configuration file /etc/nginx/nginx.conf test failed

My web server is (include version): nginx version: nginx/1.18.0 (Ubuntu)

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is: Godaddy / Cloudflare

I can login to a root shell on my machine (yes or no, or I don't know): Yes (Digital Ocean)

I'm using a control panel to manage my site (no, or provide the name and version of the control panel): No

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):0.40.0

You must still have an ssl_certificate line that names that file but it does not exist. Did you delete the certificate?

You should not need a cert for a subdomain since you have a wildcard cert for


Thanks Mike. I deleted the certificates - but Nginx trying to load it while its not existing. I have dug a bit and noticed that the subdomain certificate was being referred to in the default server block. I have commented these lines out and now Nginx configuration errors are resolved.

Thank you for checking.


This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.