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:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Error while running nginx -c /etc/nginx/nginx.conf -t.
nginx: [emerg] BIO_new_file("/etc/diaspora/ssl/chatamerica.us-bundle.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory:fopen(’/etc/diaspora/ssl/chatamerica.us-bundle.pem’,‘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):
The operating system my web server runs on is (include version): Ubuntu 18.04 Server
My hosting provider, if applicable, is:
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):
This means you have an issue with your nginx configuration. More specific: the file /etc/diaspora/ssl/chatamerica.us-bundle.pem is missing. (I suppose it's a ca-bundle)
For your benefit, I've attached the CA Bundle you needed here. Warning: hard-coding certificate/CA chains are bad practice, you should use certbot's chained certificate instead of specifying CA chain, as it'll change on July 2020. Read more here
This content will only work until July 2020. (As Let's Encrypt will use their own ISRG Root)
Do you still have the original files available?
If not, you have two options:
Remove https virtual host and remove redirections, obtain the certificate, then recover it. (This is complex…)
Generate a temporary self-signed certificate and bypass the issue, for now, run certbot.
Backup your virtual host file for both options
Option 1:
copy your virtual host configurations to a safe place.
goes into your virtual host file and copy contents from https (with port 443) to HTTP. (Be sure to remove directives that shouldn’t be in HTTP, such as sslcertificate, sslkey or protocol)
Remove your https configuration file.
Attempt to validate configuration nginx -t.
If works, obtain a certificate with certbot. Allow certbot to set up the certificate for you. (With certbot - nginx, don’t use certonly)
Option 2:
copy your virtual host configurations to a safe place.
Generate a dummy (self-signed) certificate at the required location (modify your certificate file path to the one nginx is asking for. The one with out) openssl req -x509 -newkey rsa:4096 -keyout /etc/diaspora/ssl/chatamerica.us.key -out /etc/diaspora/ssl/chatamerica.us.cert -days 5
test your Nginx configuration with nginx -t
Obtain a certificate with certbot, allow it to update configuration files.
Remove the dummy files once you obtained the certificate (the key at /etc/diaspora/ssl/chatamerica.us.key and cert at /etc/diaspora/ssl/chatamerica.us.cert or whatever it is)