Hi all,
I’ve been trying for many hours to setup DuckDNS on my RPi3 running Hass.io and have not been successful in doing so. Here is my current state:
- RPi3 with Hass.io 0.69.1 installed
- Samba share add-on successfully installed and active
- SSH Server add-on successfully installed and active
- Duck DNS add-on installed but not working
- Duck DNS account created, subdomain chosen and token generated
Here is my current Duck DNS config:
{
"lets_encrypt": {
"accept_terms": true,
"certfile": "fullchain.pem",
"keyfile": "privkey.pem"
},
"token": "x-x-x-x-x",
"domains": [
"mydomain.duckdns.org"
],
"seconds": 300
}
Here is my configuration.yaml:
homeassistant:
# Name of the location where Home Assistant is running
name: Home
# Location required to calculate the time the sun rises and sets
latitude: 0
longitude: 0
# Impacts weather/sunrise data (altitude above sea level in meters)
elevation: 0
# metric for Metric, imperial for Imperial
unit_system: imperial
# Pick yours from here: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones
time_zone: *
# Customization file
customize: !include customize.yaml
# Show links to resources in log and frontend
introduction:
# Enables the frontend
frontend:
# Enables configuration UI
config:
http:
# Secrets are defined in the file secrets.yaml
api_password: !secret http_password
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
base_url: https://mydomain.duckdns.org
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
# Checks for available updates
# Note: This component will send some information about your system to
# the developers to assist with development of Home Assistant.
# For more information, please see:
# https://home-assistant.io/blog/2016/10/25/explaining-the-updater/
updater:
# Optional, allows Home Assistant developers to focus on popular components.
# include_used_components: true
# Discover some devices automatically
discovery:
# Allows you to issue voice commands from the frontend in enabled browsers
conversation:
# Enables support for tracking state changes over time
history:
# View all events in a logbook
logbook:
# Enables a map showing the location of tracked devices
map:
# Track the sun
sun:
# Weather prediction
sensor:
- platform: yr
# Text to speech
tts:
- platform: google
# Cloud
cloud:
group: !include groups.yaml
automation: !include automations.yaml
script: !include scripts.yaml
# Z-Wave
zwave:
usb_path: /dev/ttyACM0
Contents of SSL directory:
core-ssh:~# ls -l /ssl
total 12
-rw------- 1 root root 5861 May 19 19:35 fullchain.pem
-rw------- 1 root root 3243 May 19 19:35 privkey.pem
Unsuccessful ping to Duck DNS:
XX:~ XX$ ping https://mydomain.duckdns.org/
PING https://mydomain.duckdns.org/ (**some IP address here, not mine**): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
Request timeout for icmp_seq 3
Request timeout for icmp_seq 4
Request timeout for icmp_seq 5
Request timeout for icmp_seq 6
Request timeout for icmp_seq 7
^C
--- https://mydomain.duckdns.org/ ping statistics ---
9 packets transmitted, 0 packets received, 100.0% packet loss
Unsuccessful ping to my address assigned from my ISP:
XX:~ XX$ ping XXX.XXX.XXX.XXX
PING XXX.XXX.XXX.XXX (XXX.XXX.XXX.XXX): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
Request timeout for icmp_seq 2
^C
--- XXX.XXX.XXX.XXX ping statistics ---
4 packets transmitted, 0 packets received, 100.0% packet loss
In my router, I have the following configured:
- RPi3 to static LAN IP
- Port Forwarding External 443 to 8132 for RPi3 IP
I am able to login locally over https, but receive a notice about an invalid certificate (but I can see the certified cert for mydomain):
Log from Duck DNS startup:
starting version 3.2.4
# INFO: Using main config file /data/workdir/config
+ Account already registered!
Sat May 19 22:57:17 CDT 2018: OK
XXX.XXX.XXX.XXX
NOCHANGE
# INFO: Using main config file /data/workdir/config
Processing mydomain.duckdns.org
+ Checking domain name(s) of existing cert... unchanged.
+ Checking expire date of existing cert...
+ Valid till Aug 17 23:35:30 2018 GMT (Longer than 30 days). Skipping renew!
Sat May 19 23:02:21 CDT 2018: OK
XXX.XXX.XXX.XXX
NOCHANGE
Sat May 19 23:07:22 CDT 2018: OK
XXX.XXX.XXX.XXX
NOCHANGE
Sat May 19 23:12:22 CDT 2018: OK
XXX.XXX.XXX.XXX
NOCHANGE
Sat May 19 23:17:23 CDT 2018: OK
XXX.XXX.XXX.XXX
NOCHANGE
I feel like I’m close, but probably have just one or two things misconfigured. If anyone has suggestions or an idea of what may be wrong, please let me know!
Thanks
