Being confident enough with setting up home assistance, I decided to finally set-up remote access of my home assistance away from my home LAN network via the portforward+duckdns method. I followed the great tutorial on port forwarding by Ben on BruhAutomation. https://www.youtube.com/watch?v=BIvQ8x_iTNE
I am able to access the HA instance on my home network via my Private IP [192.168.X.X:8123],the Public IP [196.X.X.X:8123] and the duckdns domain [mydomain.duckdns.org:8123].
My challenge is that I cannot access the HA instance away from my home network (lets say at work) via the Public IP [196.X.X.X:8123] and the duckdns domain [mydomain.duckdns.org:8123] options.
Does anyone know where I might be going wrong?
HA is running on a Raspberry Pi B+ and my router is a TP-Link 3G Router Model No. TL-MR3420.
My internet gateway is a modem that plugs in direct to the router.
IMy home network access the internet through a 3G router connected to a modem belonging to provider A. My primary phone line is also by provider A, but I have other phone lines by provider B and Provider C.
On my home network, I can access the HA instance via my Private IP [192.168.X.X:8123],the Public IP [196.X.X.X:8123] and the duckdns domain [mydomain.duckdns.org:8123]. Both though the laptop and phone when they are connected to the router.
If I disconnect from Wifi and try to access the home assistant instance with my phone [connected to provider A], I cannot get it to work with either the Public IP [196.X.X.X:8123] and the duckdns domain [mydomain.duckdns.org:8123] options.
I also cannot get it to connect when I switch my SIM line to provider B and C.
NB. I have used the online portchecker tool http://www.canyouseeme.org/ to check for open ports and actually I cannot find any open port [all common ports and 8120 to 8130]. Are such tools accurate? Or I should just resign myself to never using home assistant away from home.
you can absolutely use those tools.
One thing, do you have another modem or router sitting in front of your 3g router?
Because that could cause the problem.
I think you can access it from inside your network over your duckdns, because your 3g router is rerouting your request directly to your raspberry and not over the internet.
could you resolve the issue? I’m pretty sure that your provider will not give you a publicly reachable IP address. You will be most likely be behind a NAT. This means there is no possibility to connect from the outside. (unless you convince your provider to forward the ports) which he will most definitely not do and anyways most probably the terms of service will explicitly forbid you from running any kind of server.
I could be possible still if you do some ugly ssh remote port forwarding. But that would require a server available. Maybe a solution like http://www.weaved.com/ ?
@snizzleorg
I actually talked to my 3G provider this morning, and I was informed that they could set up a business VPN account for me with a static IP and open ports for a one-off fee of about $100 and a minimum post-pay data plan of $15.
It would have been great if I could have it set up and avoid the extra charges. @texnofobix
The weaved option looks very interesting. Have you used the service on a Raspberry PI? How “ugly” does it get setting it up? do you think it would cooperate with HA?
Hi all, I know this is an old topick, but I got the same problem, I got the internet from a 4g router and I can not get any port forwarding unless I pay more than the double cost for my connection. Sadly I have no other options in my location for the internet and I would prefer not to pay Bussiness price for my automation.
I’m already using weaved but there is one problem, the address often changes so it is not a valuable solution. I need to go to weaved account check my new address and then connect to my HA frontend. Does someone has found a solution for this?
