Home Assistant Having issue with cellular data

Hi Guys.

ive a very wierd issue with my home assistant with duckdns.
running home assistant 0.99.3 with duckdns addon

http:
api_password: xxxxxx

base_url: https://xxxxx.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
#ip_ban_enable: false

ive set these in my configuration.ymal file

{
“lets_encrypt”: {
“accept_terms”: true,
“certfile”: “fullchain.pem”,
“keyfile”: “privkey.pem”
},
“token”: “f2ffe3f0-bd89-4916-b44f-43d21ea182s2”,
“domains”: [
xxxxx.duckdns.org
],
“seconds”: 300
}
and these config on my duckdns addon

i can access the home assistant page from my local network as well as from remote network using wifi but unable to access thru any cellular data 3G/4G.

when connected on wifi in a remote location, im able to connect from my mobile browser (both chrome and safari) and also HA iOS app with my mobile phone but when i change to cellular data , they seems to time out for the browsers.

i hope some one can shed some light on this issue

regards mikey

Cellular carriers use CGNAT but this should not prevent you from accessing Home Assistant via DuckDNS from your mobile. It would only be a problem if your Home Assistant server was connected via this sort of carrier.

Perhaps your cellular provider blocks certain ports?

Have you tried using (and forwarding) port 443 instead of 8123?

Hi Tom,

Yes . I have tried to forward a a few ports to try . 80 to 8123 , 443 to 8123 , 8123 to 8123 but all still yield the same result.

My cellular data runs on cgnet but it should not affect the resolve the host.

** as of testing as I write this , I’ve added up_ban_enable : false which when I use my cellular data browser to connect into the the link but stop shy on initializing showing on the screen. Maybe it is due to cache .

Hello everyone, I know it’s an old topic but I spend last two days figuring out why I can’t remotely access my HA. Unfortunately I couldn’t find solution here on forum so I decided to share my experience and how I found solution.

Everything was working great for almost a year, but after latest updates I couldn’t reach my HA remotely over Android phone (3G, 4G doesn’t matter). Pretty much same as @Chew_Yikai. Result was HA screen saying: Unable to connect to Home Assistant. RETRY

What bothered me most is that I was able to reach HA remotely over cellular when I activate VPN app on my phone.

I was playing with “Whats my IP” little bit and figured out that without VPN my phone has IPv6 and IPv4 address, and with VPN only IPv4.

I looked in Phone network settings and created new APN profile, where I practicaly copied everything from original one except APN protocol where I chose IPv4 (original had IPv4/IPv6). After phone restart and couple of minutes I was able to reach my HA remotely over 3G/4G without any issues.

Maybe someone can explain why is that so, and what changes in HA could cause this. It seems impossible to me that my cellular service provider made some changes with protocols exactly at same point when I updated my HA, because everything worked before HA update. Also I had both IPv4 and IPv6.

In any case this might help someone with same issue to resolve it, at least for some time. For how long, we’ll see.

2 Likes

Hi CrazyEngineer,

For my case i was having Double NAT on my Cellular Network.
My Setup was having 2 cellular network , one connected to my home network providing data to the whole house, another is my mobile phone.

When accessing thru same service provider, i was unable to access it directly . But if i turn on VPN on my mobile phone, i was able to access it normally.

Regards
Mike