I’ve been following the tutorial to get DuckDNS up and running with Let’s Encrypt and just cannot get the SSL certificate to work.
Here is what I have
{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": "mytoken",
"domains": [
"mydomain.duckdns"
],
"seconds": 300
}
Log Message:
# INFO: Using main config file /data/workdir/config
+ Account already registered!
Sat Nov 10 02:03:07 UTC 2018: OK
72.65.252.97
NOCHANGE
# INFO: Using main config file /data/workdir/config
Processing snautomation.duckdns.org
+ Checking domain name(s) of existing cert... unchanged.
+ Checking expire date of existing cert...
+ Valid till Feb 8 00:23:46 2019 GMT (Longer than 30 days). Skipping renew!
It successfully created the certs. I see them living in the \ssl folder.
Here is the config file
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
http:
base_url: mydomain.duckdns
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
# Checks for available updates
I’ve tried various combinations of https:\mydomain.duckdns, putting all the values in quotes. Nothing works.
I have port forwarding set up for 80, 443, and 8123 all pointing to 8123. I can access all the sites through http.
http:\mydomain.duckdns:443, mydomain.duckdns:8123 all work for example.
When I go to load the https:\mydomain.duckdns, it just won’t load at all.
Browser gives me a secure connection failed error.
Any assistance would be vastly appreciated.
edit: Note, I had to remove .org from all the “urls” so that I could post.