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:
https://stage.uhero.hawaii.edu/ (not publically accessible)
I ran this command:
It produced this output:
My web server is (include version):
nginx/1.12.1
The operating system my web server runs on is (include version):
RHEL6
My hosting provider, if applicable, is:
Self, on a vm managed within university IT services
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): no
I'll try to keep this brief and to the point: I'm sure this cert was working correctly at one time. Thankfully it is for a staging server, not production, thus not really important, but I guess I need to know why it's breaking:
$ sudo ./certbot-auto certificates
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Found the following certs:
Certificate Name: stage.uhero.hawaii.edu
Domains: stage.uhero.hawaii.edu stage-api.uhero.hawaii.edu stage-data.uhero.hawaii.edu
Expiry Date: 2019-01-21 00:49:15+00:00 (VALID: 47 days)
Certificate Path: /etc/letsencrypt/live/stage.uhero.hawaii.edu/fullchain.pem
Private Key Path: /etc/letsencrypt/live/stage.uhero.hawaii.edu/privkey.pem
also
$ sudo ./certbot-auto renew
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Processing /etc/letsencrypt/renewal/stage.uhero.hawaii.edu.conf
Cert not yet due for renewal
The following certs are not due for renewal yet:
/etc/letsencrypt/live/stage.uhero.hawaii.edu/fullchain.pem expires on 2019-01-21 (skipped)
No renewals were attempted.
IOW, everything looks ok. But when I go to the site in Firefox or Chrome, I get the standard Your connection is not secure
warning. Note that this server is behind firewalls and you won't be able to access it from outside. Hope that's not really necessary to get help. If you're wondering how I did the original cert install and renewals, I have a script that pokes open the firewall before doing cronned renewal task, and then closes it again. I believe the script is working correctly, but I don't think that's relevant to my problem. Can someone help? Thanks.