Fullchain.pem and privkey.pem are missing

bengt · December 31, 2018, 10:16pm

Hi.
I have just installed HassIO (0.84.6), and I’m having a problem when I try to connect to HassIO trough https://mydomain.duckdns.org:8123. Works fine tith http://…

Configuration.yaml

        http:
          base_url: mydomain.duckdns.org:8123
         ssl_certificate: /ssl/fullchain.pem
         ssl_key: /ssl/privkey.pem

DuckDNS config in

    {
      "lets_encrypt": {
        "accept_terms": false,
        "certfile": "fullchain.pem",
        "keyfile": "privkey.pem"
      },
      "token": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
      "domains": [
        "https://mydomain.duckdns.org"
      ],
      "seconds": 300
    }

Problem seems to be that the SSL folder is empty. This folder should contain the files fullchain.pem and privkey.pem?
Can the files be stored in another location, or is there any way I can generate new files?

Crhass · December 31, 2018, 10:30pm

If you change accept_terms to true in your config does that generate the files?

bengt · January 1, 2019, 12:12am

No, that did not help

Log in Duck DNS:

# INFO: Using main config file /data/workdir/config
+ Account already registered!
Tue Jan  1 01:02:43 CET 2019: KO
# INFO: Using main config file /data/workdir/config
Processing https://my_domain.duckdns.org
 + Signing domains...
 + Generating private key...
 + Generating signing request...
end of string encountered while processing type of subject name element #1
problems making Certificate Request

Crhass · January 1, 2019, 9:24am

Try https:// in your base url

bengt · January 1, 2019, 4:36pm

Have tried https:// in base url to, and restarted but still no .pem files.
Have formatted the SD card and installed HassIO one more time… still the same problem.

(Installed add-ons are: Configurator, Duck DNS and SSH server).

flamingm0e · January 1, 2019, 4:39pm

Https:// is not a valid domain name.

Crhass · January 1, 2019, 4:44pm

I also have this in my config yaml but not sure if it’s needed?

duckdns:
  domain: subdomain
  access_token: duckdnstoken

Crhass · January 1, 2019, 4:44pm

I hope he had put the full URL and not just https://

flamingm0e · January 1, 2019, 4:46pm

No. Https:// doesn’t need to be in base URL.

I’m referring to the duckdns config. Under domains. Https:// is not a domain name.

casey-hill · January 1, 2019, 4:47pm

for the domain … its not correct.

use the exact syntax

“mydomain.duckdns.org” using the quotes.

Your configuration.yaml, the spacing looks wrong for ssl_certificate and ssl_key… they should be over just a bit farther to the right.

flamingm0e · January 1, 2019, 4:49pm

The files aren’t being created because the duckdns config is incorrect

Crhass · January 1, 2019, 4:50pm

Is the duckdns section still required in config yaml or can I remove that?

flamingm0e · January 1, 2019, 4:51pm

Duckdns component has nothing to do with the add-on. If you weren’t using hassio and wanted to update your duckdns name, you would use the component

Crhass · January 1, 2019, 4:54pm

Oh yeah, I will remove it then, I have probably been updating my IP with 2 systems.

If you are running the Hass.io DuckDNS add-on this component is not required. The add-on will keep your IP updated with DuckDNS.

GeoffState · March 26, 2023, 7:30am

Wicked -that worked for me.

Abdo7085 · November 3, 2024, 12:41pm

accept_terms: true
algo: secp384r1
certfile: fullchain.pem
keyfile: privkey.pem

worked