Remote Access not working

1

Hello,

I’m new to Home Assistant. Got HA working locally. However I can’t get Duck DNS remote access working. I’ve tried using 4G on my smartphone to see if the problem was in my internal network - it isn’t.

I’ve installed Duck DNS add-on (as explained bij Juan M Tech and PinkyWafer on YouTube).
In /config/configuration.yaml the part where it’s supposed to say:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
# http:

wasn’t there so I manually added this:

# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
 http:
   base_url: myduckdnsname.duckdns.org.duckdns.org
   ssl_certificate: /ssl/fullchain.pem
   ssl_key: /ssl/privkey.pem
   ip_ban_enabled: True
   login_attempts_treshold: 3

Since I use my Asus router behind my ISP’s modem-router I port forwarded 8123 to 8123 on both. I forwarded 8123 on my ISP’s modem-router to it’s local ip of my Asus router and on the Asus router to my local HA ip address. Port 443 is already used by another application on my network.

In the configuration part of the Duck DNS add-on I have:

lets_encrypt:
  accept_terms: true
  certfile: fullchain.pem
  keyfile: privkey.pem
token: copied my token from Duck DNS here
domains:
  - mydomainname.duckdns.org
aliases: []
seconds: 300

What am I doing wrong? How can I fix this?

2

Hi Ramon,

Glad to see this topic. I got the same problem. I followed the steps in the video and also looked some other videos. They did all the same. Hope somebody can help us with this…

kr,
Kevin

3

Just to be sure, I’ve checked; in a browser on my phone (on 4g, so outside of my home network) my Duck DNS domain leads to port 5000 of my Synology NAS. If I manualy change the port to :8123 (http://myname.duckdns.org:8123 ) at the end of the URL I get a ERR_CONNECTION_TIMED_OUT in the browser. So I do have a connection from the outside to my network, but can’t reach Home Assistant. From what I can tell the error originates in Home Assistant itself.

I am running HA on a Raspberry Pi 4B.

4

Did you get this resolved? First, it looks like you have duckdns.org twice in your config. I don’t have anything in my config, only in DuckDNS and NGINX configurations (in integrations). Mine is setup this way… port forward 443 in the router to the HA IP, (not necessarily the NAS IP, depending on setup) / port 443. I am using https://xxxx.duckdns.org (no port) as my remote address. The traffic should go like this:
Internet (https/port 443) to router, router forwards incoming port 443 to HA IP address port 443 / NGINX. I hope that helps.