Missing SSL certificate

Configuration
1

Hi,

I’ve mistakenly deleted certificates from SSL folder and don’t know how to re-generate them. Actually I was trying to establish https connect using duckdns, it was not running and after long trying various things, I deleted certificates with the hope that DuckDNS add-on will re-generate it. Seems that was wrong idea. Sorry, I’m not familiar how does it work.
So, for now I need to restore certificates, then I’ll continue digging why my hassio is not accessible from outside (I followed detailed instructions but something is wrong).
I have following addons running: Configurator, Duck DNS, SSH Server, Samba share. I also have Let’s Encrypt addon installed but stopped at the moment.
I’m aware of openssl.org, just can’t get it running on my windows pc. Is there more simple way to re-generate certificate from hassio directly.

2

restart the duckdns add-on

1 Like
3

Hmm, restarting DuckDNS doesn’t create certificates (I tried also before with same result). Log says:

# INFO: Using main config file /data/workdir/config
+ Account already registered!
Tue Apr 23 20:46:51 CEST 2019: OK
XXX.YY.ZZZ.NN (my IP)
NOCHANGE
# INFO: Using main config file /data/workdir/config
Processing myname.duckdns.org
 + Checking domain name(s) of existing cert... unchanged.
 + Checking expire date of existing cert...
 + Valid till Jul 13 12:54:16 2019 GMT Certificate will not expire
(Longer than 30 days). Skipping renew!

Then I restarted PI by removing power. After restart I’ve lost http access (neither https://192.168.1.10:8123 nor 192.168.1.10 work). However I still have access to files by Samba and ssh. Then I commented http section in configuration.yaml and restarted again. Same behaviour.
Seems something wrong in general and I’ll need to re-install complete system :frowning:

4

It would seem you didn’t actually delete the certs. If you had actually deleted the certs it would activate as if it were a new domain.

5

I have exactly the same problem, accidentally I removed PEM files.
When I try to restart DuckDNS add-on, it is not recreating the files in /ssl folder.
Even if I change the accept_terms to false and back to true.

How does it possible to recreate it?

I was trying to remove the add-on, then intall it again, with the same setting like before, I got this:

[18:03:46] INFO: Renew certificate for domains: honved100.duckdns.org and aliases:

INFO: Using main config file /data/workdir/config

  • Creating chain cache directory /data/workdir/chains
    Processing honved100.duckdns.org
  • Creating new directory /data/letsencrypt/honved100.duckdns.org …
  • Signing domains…
  • Generating private key…
  • Generating signing request…
  • Requesting new certificate order from CA…
  • Received 1 authorizations URLs from the CA
  • Handling authorization for honved100.duckdns.org
  • 1 pending challenge(s)
  • Deploying challenge tokens…
    OK + Responding to challenge for honved100.duckdns.org authorization…
  • Challenge is valid!
  • Cleaning challenge tokens…
    OK + Requesting certificate…
  • Checking certificate…
  • Done!
  • Creating fullchain.pem…
    cp: can’t create ‘/ssl//ssl/fullchain.pem’: No such file or directory
    ERROR: deploy_cert hook returned with non-zero exit code
    Blockquote

The problem is : cp: can’t create ‘/ssl//ssl/fullchain.pem’: No such file or directory
How does it possible?
Before you ask, in the config is this:

aliases:
domains:

  • mydomain.duckdns.org
    lets_encrypt:
    accept_terms: true
    algo: secp384r1
    certfile: /ssl/fullchain.pem
    keyfile: /ssl/privkey.pem
    seconds: 300
    token: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

So the directory names are correct in the config file, but somehow DuckDNS add-on doesn’t handle it correctly…
Any idea?

6

It is shocking to me just how many folks are struggling with this same problem. I deleted my PEM Files and now need them to revoke the certs.

How on earth does one recreate them? “Rerunning” DuckDNS or LetsEncrypt says the certs are still valid, so it DOES NOT recreate the files, contrary to what some posters say. It seems like these add-on need to be revisited by the devs to solve this all to common problem so many of us have…