Hello
This is my second attempt at HA. First time I go it down loaded bet then was unable to get in configurator and basiclly froze myself out. So I started all over. NOW I cannot get duckDNS to work or letencrypt and my sambashare is working but the SSL file is empty. I have seen many videos using PUTTY to back door the system but I have realized mine always says the files are not there. So did I not download everything?
My DuckDNS log
INFO: Using main config file /data/workdir/config
- Account already registered!
Thu Jan 17 23:09:35 UTC 2019: KO
INFO: Using main config file /data/workdir/config
Processing http://[email protected]
- Signing domains…
- Generating private key…
- Generating signing request…
end of string encountered while processing type of subject name element #1
problems making Certificate Request
My letsencrypt log
Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator standalone, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for example.com http-01 challenge for mqtt.example.com http-01 challenge for hass.example.com Waiting for verification… Cleaning up challenges Failed authorization procedure. mqtt.example.com (http-01): urn:acme:error:dns :: DNS problem: NXDOMAIN looking up A for mqtt.example.com, example.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://example.com/.well-known/acme-challenge/n3KU50tHKv6GrajN0MANhT3D9HxXfrWu1PH4ZbkLmss: "<!doctype html>\n<html>\n<head>\n <title>Example Domain</title>\n\n <meta charset=“utf-8” />\n <meta http-equiv=“Content-type”, hass.example.com (http-01): urn:acme:error:dns :: DNS problem: NXDOMAIN looking up A for hass.example.com IMPORTANT NOTES: - The following errors were reported by the server: Domain: example.com Type: unauthorized Detail: Invalid response from http://example.com/.well-known/acme-challenge/n3KU50tHKv6GrajN0MANhT3D9HxXfrWu1PH4ZbkLmss: "<!doctype html>\n<html>\n<head>\n <title>Example Domain</title>\n\n <meta charset=“utf-8” />\n <meta http-equiv=“Content-type” To fix these errors, please make sure that your domain name was entered correctly and the DNS A/AAAA record(s) for that domain contain(s) the right IP address. - The following errors were reported by the server: Domain: mqtt.example.com Type: None Detail: DNS problem: NXDOMAIN looking up A for mqtt.example.com Domain: hass.example.com Type: None Detail: DNS problem: NXDOMAIN looking up A for hass.example.com