I ran this command: sudo certbot certonly --webroot -w ./public/ -d harel.ddns.net
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Cert not yet due for renewal
You have an existing certificate that has exactly the same domains or certificate name you requested and isn’t close to expiry.
(ref: /etc/letsencrypt/renewal/harel.ddns.net.conf)
My web server is (include version): Node (4.2.1) + Express (4.14)
The operating system my web server runs on is (include version): (Raspberry Pi Debian Jessie)
Found the following certs:
Certificate Name: harel.ddns.net
Domains: harel.ddns.net
Expiry Date: 2018-12-07 11:30:28+00:00 (VALID: 89 days)
Certificate Path: /etc/letsencrypt/live/harel.ddns.net/fullchain.pem
Private Key Path: /etc/letsencrypt/live/harel.ddns.net/privkey.pem
So I have a certificate that is not expired yet.
From my Express app - I can’t access the .pem files. So what I did is I copied them into another folder, chown them for the user that runs the web server (pi) and point my Express app to that.
I even run
openssl verify -CAfile chain.pem cert.pem
and that returns OK.
I know it has a time out - this is why I’m asking for help here. About the multiple active certificates - this is me trying to troubleshoot this situation.
Everything seems to be configured correctly but still https://harel.ddns.net returns an error with ERR_CERT_INVALID