DuckDNS - Numpty requires a poke in the right direction please

Configuration
1

Hello All,

Thanks in advance, in a nutshell…

Installed Hassio on RPi3 2 days ago and duckdns is not working and I am not sure where to even catch logs in HA. IF they will shed any light on what I have done wrong!!!

  • Installed Hassio
  • Installed DuckDNS
  • Registered domain on DuckDNS.org and copied token
  • Read lets encrypt ts and cs (honest guv)
  • Changed configuration to and saved
lets_encrypt:
  accept_terms: true
  certfile: fullchain.pem
  keyfile: privkey.pem
token: dxxxxxxxxxxxxxxxxxxxxxxxxxxxxx83
domains:
  - xxxxxxxxx.duckdns.org
seconds: 300
  • Started the app in Hassio
  • Log all came back positive
  • Pings for IP address came back ok
  • portforwarded 8123 to 8123 on my RPi3 ip address on the router.
  • went to a web browser to https://xxxxxxxx.duckdns.org
  • No response just times out
  • put my external ip address with the :8123 port and it comes to the login screen for my hassio gui. (not secure as padlock was crossed out)

Any ideas where I can look to se what is occuring. I have had this up an running with an older version, where it used to be setup in config.yaml but not with the newer hassio.

Any suggestions would be appreciated.

Kind REgards

Rob

2

should be 443 to 8123

3

thanks for a quick reply.

  • changed port forward from 443 -> 8123

  • xxxxxx.duckdns.org came back with an error.

  • put in my xxx.xxx.xxx.xxx:443 (exteranl IP) and came to HA gui login (unsecure)

  • if I try to use https:// get the following in firefox

    Error code: SSL_ERROR_RX_RECORD_TOO_LONG

Thanks
Rob

4

you have to use your dns name, i.e. https://xxxx.duckdns.org for external and internal access

5

Thanks Petro.

I am heading in the right direction now.

if I type in either inside or outside of my network, I get a secure connection.

https://xxxxxx.duckdns.org:8123

But is it possible to achieve this without having to type the port number? If i remove it I can not connect.

Regards

Rob

6

If you forward 8123 -> 8123, you need to type in the port, the URL for inside and outside stays the same
if you forward 443 -> 8123, you don’t need to type in the port from outside, but if your router does hairpinning, you will still need to add :8123 from inside your lan.

7

Perfect thank you both for your time, much appreciated.

Regards

Rob

8

Hi, can I hijack this thread as I’m seeing something related but not sure if I should be.

I’m using duckdns, and went through the steps. Had lots of issues with port forwarding.

My vodafone router (new one on the way) wouldnt allow me to port forward 8123 > 8123, with the error message Corrections needed, Duplicate Ports Found.
It is currently set to forward 443 > 8123 which was also advised, which it accepted.

When I access HA from outside my network using https://XXXXXXX.duckdns.org, it allows me through to the log in page without any issues. If I use the same address within my network, same results.
However, if I use https://xxxxxxxx.duckdns.org:8123 it states unable to connect both within and outside my network.

Technically it is working as I can access, however is this ok? Am I going to run into any issues down the line?

For example, I’ve set up alexa local integration and had it point to …duckdns.org without the port. It works, but will it brake in the future?

Thanks for any help

9

No, that’s how it works. 443 is forwarded to 8123 so you just omit the port when connecting through the url.

10

Great thank you