Can't connect HA to the internet but works fine locally

maco2035 · November 10, 2024, 3:53pm

This might help to find something:

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
 106K   16M DOCKER-USER  0    --  *      *       0.0.0.0/0            0.0.0.0/0           
 106K   16M DOCKER-ISOLATION-STAGE-1  0    --  *      *       0.0.0.0/0            0.0.0.0/0           
  978 82701 ACCEPT     0    --  *      docker0  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
    0     0 DOCKER     0    --  *      docker0  0.0.0.0/0            0.0.0.0/0           
 7038  432K ACCEPT     0    --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
    0     0 ACCEPT     0    --  docker0 docker0  0.0.0.0/0            0.0.0.0/0           
59894   13M ACCEPT     0    --  *      hassio  0.0.0.0/0            0.0.0.0/0            ctstate RELATED,ESTABLISHED
 4567  290K DOCKER     0    --  *      hassio  0.0.0.0/0            0.0.0.0/0           
33740 2232K ACCEPT     0    --  hassio !hassio  0.0.0.0/0            0.0.0.0/0           
 4567  290K ACCEPT     0    --  hassio hassio  0.0.0.0/0            0.0.0.0/0           

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.32.6          tcp dpt:80
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:8889
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:8888
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:8554
    0     0 ACCEPT     17   --  !hassio hassio  0.0.0.0/0            172.30.33.2          udp dpt:8189
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:5000
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:1935
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.3          tcp dpt:1627

Chain DOCKER-ISOLATION-STAGE-1 (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 7038  432K DOCKER-ISOLATION-STAGE-2  0    --  docker0 !docker0  0.0.0.0/0            0.0.0.0/0           
33740 2232K DOCKER-ISOLATION-STAGE-2  0    --  hassio !hassio  0.0.0.0/0            0.0.0.0/0           
 106K   16M RETURN     0    --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-ISOLATION-STAGE-2 (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 DROP       0    --  *      docker0  0.0.0.0/0            0.0.0.0/0           
    0     0 DROP       0    --  *      hassio  0.0.0.0/0            0.0.0.0/0           
40778 2664K RETURN     0    --  *      *       0.0.0.0/0            0.0.0.0/0           

Chain DOCKER-USER (1 references)
 pkts bytes target     prot opt in     out     source               destination         
 106K   16M RETURN     0    --  *      *       0.0.0.0/0            0.0.0.0/0

WallyR · November 10, 2024, 5:19pm

Well, something is amiss.

Chain FORWARD (policy DROP 0 packets, 0 bytes)
 4567  290K DOCKER     0    --  *      hassio  0.0.0.0/0            0.0.0.0/0

This shows that 290K data have been sent to the DOCKER chain.

Chain DOCKER (2 references)
 pkts bytes target     prot opt in     out     source               destination         
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.32.6          tcp dpt:80
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:8889
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:8888
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:8554
    0     0 ACCEPT     17   --  !hassio hassio  0.0.0.0/0            172.30.33.2          udp dpt:8189
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:5000
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.2          tcp dpt:1935
    0     0 ACCEPT     6    --  !hassio hassio  0.0.0.0/0            172.30.33.3          tcp dpt:1627

This shows that no data have been handled in the DOCKER chain.

It looks like the hassio is not set up to have host permissions in docker.
Are you running Portainer by any chance?

nickrout · November 10, 2024, 6:22pm

Are you really running HAOS? Or some other install method?

maco2035 · November 10, 2024, 7:15pm

I am running this in haos. 100% postive, as I had to manually type my ssh keys into the console in my basement

I don’t know what is happening in the iptables.

There is no containters.

What I have installed in my machine:
HACS
Duckdns add on
Wiregaurd add on (off and uninstalled now)
Grocy add on (off)
Wyze add on

WallyR · November 11, 2024, 7:11am

Looking at all this info and I can only see one place for the issue to be located and that is your router.

nickrout · November 11, 2024, 8:21am

This is from your first post. What filetime is this exactly (full path and name please)

Also please go to Settings/About. Tell us what you see there

Core
2024.11.1
Supervisor
2024.11.3
Operating System
13.2
Frontend
20241106.2

maco2035 · November 11, 2024, 3:06pm

I have done a full factory reset on the router and it still has issues.

maco2035 · November 11, 2024, 3:07pm

It looks old because I am unable to update it.
This is from today:

Core 2024.9.3
    Supervisor 2024.10.3
    Operating System 13.1
    Frontend 20240909.1

Welcome to Home Assistant OS.

Use `ha` to access the Home Assistant CLI.
# ha network info
docker:
  address: 172.30.32.0/23
  dns: 172.30.32.3
  gateway: 172.30.32.1
  interface: hassio
host_internet: false
interfaces:
- connected: true
  enabled: true
  interface: eno1
  ipv4:
    address:
    - 192.168.1.217/24
    gateway: 192.168.1.1
    method: static
    nameservers:
    - 192.168.1.1
    ready: true
  ipv6:
    address:
    - fdb8:b56f:def3:b34c:390b:a643:952a:d878/64
    - fe80::1e43:a84b:ef42:df51/64
    gateway: null
    method: auto
    nameservers: []
    ready: true
  mac: 98:90:96:D4:05:B7
  primary: true
  type: ethernet
  vlan: null
  wifi: null
supervisor_internet: false

maco2035 · November 11, 2024, 3:10pm

This is my routers port forwarding

u

WallyR · November 11, 2024, 4:09pm

I do not think it is your portforwarding rule, but rather a firewall rule or some defect with your router.
Have you tried restarting it?

maco2035 · November 12, 2024, 6:13pm

I have factory reset my router, and also restarted it a few times. The router is on the factory settings.

maco2035 · November 12, 2024, 6:14pm

Yes I have, I posted it below the photo of it.

nickrout · November 12, 2024, 6:26pm

Here is mine. A few differences in settings

~ # ha network info
docker:
  address: 172.30.32.0/23
  dns: 172.30.32.3
  gateway: 172.30.32.1
  interface: hassio
host_internet: true
interfaces:
- connected: true
  enabled: true
  interface: enp0s18
  ipv4:
    address:
    - 192.168.20.84/24
    gateway: 192.168.20.1
    method: auto
    nameservers:
    - 192.168.20.1
    ready: true
  ipv6:
    address:
    - fe80::67c6:43f7:d18b:cb8d/64
    gateway: fe80::2a5:4cff:fe68:1331
    method: auto
    nameservers: []
    ready: false
  mac: 02:9D:8A:03:82:C3
  primary: true
  type: ethernet
  vlan: null
  wifi: null
supervisor_internet: true

maco2035 · November 13, 2024, 9:17pm

Yeah I have no clue whats different anymore.

nickrout · November 13, 2024, 9:40pm

Mine has host_internet: true
Mine has method: auto in the ipv4: section1.
yours has gateway: null in the ipv6: section, mine has an address.
Mine has ready: false in the ipv6: section
Mine has supervisor_internet: true

I am by no means an expert on internet settings (particulalarly ipv6), but I would think one of the following might be a problem;

you having ipv6 enabled, but no ipv6 gateway. or
supervisor_internet being turned off.

maco2035 · November 13, 2024, 9:59pm

Sorry I didn’t mean any disrespect. I am sorry if my tone was incorrect.

What I mean, is that I have settings that are almost the same, but just defined by the user which is the same on the router, and the machine.

I have turned off ipv6 and I have similar problems still.

supervisor_internet is what is broken.

Thanks again for all your help!

nickrout · November 14, 2024, 3:40am

I didn’t read that into your reply at all.

WallyR · November 14, 2024, 7:04am

I think this is just a sensor, so the lack of internet will automatically make it false.

Auto just means DHCP is used to assign the IPv4 address.
It is not best method, but it should work.

Yours have a gateway for a fe80 network, which is a non-routable network, so it is an invalid gateway.

This is a sensor too and the lack of a working gateway would probably make it false

I think this is just a sensor, so the lack of internet will automatically make it false.

maco2035 · November 15, 2024, 10:27pm

Thanks Wally!

I turned off ipv6 in my router. I can turn it on and report back what changes.

maco2035 · November 15, 2024, 10:41pm

I enabled ipv6, and this is what I have.

docker:
  address: 172.30.32.0/23
  dns: 172.30.32.3
  gateway: 172.30.32.1
  interface: hassio
host_internet: false
interfaces:
- connected: true
  enabled: true
  interface: eno1
  ipv4:
    address:
    - 192.168.1.217/24
    gateway: 192.168.1.1
    method: auto
    nameservers:
    - 192.168.1.1
    ready: true
  ipv6:
    address:
    - 2600:4040:7b95:6900:17b2:95b7:efe6:bfb4/64
    - fdb8:b56f:def3:b34c:390b:a643:952a:d878/64
    - fe80::1e43:a84b:ef42:df51/64
    gateway: fe80::baf8:53ff:fe2e:74e9
    method: auto
    nameservers:
    - 2600:4040:7b95:6900::1
    ready: true
  mac: 98:90:96:D4:05:B7
  primary: true
  type: ethernet
  vlan: null
  wifi: null
supervisor_internet: false