Hi all,
I have been browsing forums and everything for over a month now, but I cant find how to fix connection to my HA server.
I have HASSIO installation on RP4. It has been working for over a year. It runs from SSD.
The server appears to be running OK, I can connect to supervisor, I can ping it and I can access CLI, when connected directly with keyboard and monitor.
I tried updating HA version, downgrading version and still both homeassistant.local:8123 and 192.168.68.66:8123 arent accessible from none of my devices.
When pinging I noticed the homeassistant.local goes to IPv6.
When connected to CLI it shows
System information
IPv4 addresses for eth0: 192.168.68.66/22 #in one thread i found that this shouldnt be 22, but didnt find out what can I do about that
IPv6 addresses for eth0: (ipv6 address...)
IPv4 addresses for wlan:
OS Version: Home Assistant OS 10.3
Home Assistant Core: 2023.7.2
Home assitant URL: http://homeasssitant.local:8123
Observer URL http://homeasssitant.local:4357
dns info:
fallback: true
host: 172.30.32.3
llmnr: true
locals:
- dns://31.30.90.11
- dns://31.30.90.12
mdns: true
servers:
- dns://8.8.8.8 #I added this based on a suggestion on another post, but it should do nothing for me since I am trying to connect on LAN
udate available: false
version: 2023.06.2
version_latest: 2023.06.2
before it started missbehaving I was trying to use duckDNS but i never got it working since I didn’t have static IP for my connection from my ISP, then I got the statick IP and after next update of HA (to version 2023.6.0) the problems started.
My HA server is connected by cable to my router and should not be in touch with ISP modem at all, I removed all rules that I was trying to port forward the 8123 port etc.
I removed the DuckDNS from my HA server since then. Restarted, upgraded, downgraded…
I Have no idea what to do next.
I realize that I might need to provide addonitional info, but I have no idea what is needed more.
What ip address does your computer have? Or any other device from which you try to connect.
Is it in the same subnet? If not, try to put it in the same subnet to check if it’s reachable.
If you are using a subnet, is network traffic between subnets allowed (my router has it’s own option for that)? Are there any firewall rules which blocks traffic to HA?
Are you using VLAN?
You can turn off IPv6 in the network settings if you don’t need it. Settings → System → Network Settings → select the interface → IPv6 and disable (make sure IPv4 isn’t disabled before saving)
yes all the devices are on the same subnet. there is only one network (and I check just to be sure) Everything runs on 192.168.68.X
there shouldn’t be any firewall settings blocking traffic to it. I do not have any rules set for this in the router and I can’t connect from any device including the app in the phone.
I do not use VLAN, there is only one network running on two mash units of Deco X20
What you also could try is to watch the route with tracert in the commandline from your computer.
Command is “tracert 192.168.68.66”
If it’s going beyond your modem then your router doesn’t know the HA i guess.
Did you set up the ip of HA static (manually entered it in the HA network settings) or via the dhcp server from your router?
ok, i don’t know why you get 192.68.66/22( normal is /24 ) , but that has to do with your Router/ISP, And docker has /23(as it should)
But your name-server(IPv4) seems “wrong” should be the same as gateway(meaning your Router)
type : net -h and go on from there try Change your nameservers: to - 192.168.68.1
EDIT: check your Router to see whether this (22 comes from there) and change that if possible(optional)
EDIT2: And if you can check your psychical NIC make sure you also got the right network mask setting (255.255.252.0) For /22
thanks I’ll start with the name servers, they came from ISP, this must have happened after I switched to public IP with my ISP (i guess)
I have no idea how to change the /22 what do you mean by physical NIC?
I’m not sure that it has something to do with the dns but who knows, some settings in HA also need an active internet connection to be saved so i won’t be surprised
It works anyway, only if HA’s internet access is blocked it won’t work. This setting won’t affect direct access via HA’s ip but like i said, he should try it
True, but his settings are wrong anyway, as he has removed DuckDns, and run HA entirely local, who know his Mdsn has his external ip pointed to HA, so it’s better to make sure all settings are default “again” , Mdns should be flushed after
EDIT: the ISP should only provide dns on the wan-connection not lan, the Router should fix this
try Change your nameservers: to - 192.168.68.1
