I’m having trouble getting my router to forward myname.duckdns.org:8123 to my Pi3 running hass.io. I’ve seen a lot of different guides on this, but it sounds like all router software have a slightly different way to do it. Here’s what I know:
I have a Linksys WRT1900ACS that comes with the linksyssmartwifi.com interface. (I’m hoping this is a fairly common interface that someone can help me navigate.)
myname.duckdns.org is correctly forwarding to my router admin page. When I add the port (myname.duckdns.org:8123), Chrome gives me: “This site can’t be reached” ERR_CONNECTION_REFUSED
In linksyssmartwifi.com, I attempted to set this up by going to Security -> Apps and Gaming -> Single Port Forwarding and set up a record with the following details: App name: hassio.local / External Port: 8123 / Internal Port: 8123 / Protocol: Both / Device IP#: my Pi IP / Enabled: checked – does this sound like the right place and details to anyone?
I’ve verified that I’m entering the correct IP for my Pi by browsing to that address and logging in to the interface.
Any advice? Anyone with a linksys router using the linksyssmartwifi.com software set this up before? Thanks!
Thank you. I already have a configured router and am familiar navigating the interface. But where do I go to forward DuckDNS? I’m looking at the following:
On a wim, I tried connecting to myname.duckdns.org:8123 while I was at work, and I can access it now. I haven’t changed any settings though, so I’m assuming I just have an issue with myname.duckdns.org:8123 working within my home network. Any ideas what that could be? I’d love to be able to use the same link regardless of where I am.
Your router needs to support loop-back in order to allow connecting to an internal address via the public domain. Most home routers do not. As a work around, create a custom DNS entry (if support by your linksys) where myname.duckdns.org points to the internal IP of your Pi3.
Thanks for your feedback. I was able to get it to work by disabling “Filter Internet NAT redirection” under Settings > Firewall tab > Internet filters
I’m unaware of the security consequences, so I’m not sure if this is a good solution for the long term, but I thought I’d respond anyway. myname.duckdns.org:8123 now works from in or outside the network.