Hello everyone,
today I installed an external fiber modem in combination with a FritzBox 7530.
Since then, HomeAssistant can unfortunately only be reached via the IP in the local network. The local IP does not change and is still the same static IP.
Neither homeassistant.local or the call via DuckDNS works. I’m not sure what the problem is and need your help.
HA runs as a VM on an Unraid server.
Lack of local access is more concerning. Does the new router have the same DHCP IP address range as the old one?
Is the gateway setting the same?
Once you have that working we’'ll work on remote access via DuckDNS (you probably just need to add the port forwarding rules again). But one thing at a time. Get local access first.
Hi tom,
the router is still the same. DHCP range, port settings nothing changed and HA has the same local static IP (.57).
The only thing that has changed is that the internal modem is no longer used, but an external one for the fiber optic connection.
I can also ping homeassistant.local via windows, but I still get the error “Unable to connect to Home Assistant.” via the browser.
A new modem probably alsp.means a new public IP, whi h means duckdns needs to Be updated.
I am not really sure what Part of the setip that actaully do that since I do not use it, but if you do not know it yourself, then restart the host (not just the core).
Then I am at a loss as to why you don’t have local access.
Maybe the following could point us in the right direction. I just noticed that in the network overview HA and Philips Hue use the same Lan port.
Before the changeover, only three devices were physicaly connected.
After - LAN 1 became the WAN port for the fiber modem.
I don’t know if HA was connected under LAN 2 before the changeover. Maybe this is causing the error?
Right, but our public IP changes every 24h in general. But that was already the case before.
where was the old modern in the before case… how did it connect to the router of you only had those three before?
Start simple. Can you ping the Home Assistant IP address?
Far from it.
There is a lease time set by the ISP and the router will try to renew a while before it reach that.
Often the router will get the same IP as earlier, because that means connected connections do not have to be dropped.
It probably was an the ARP table have not been flashed or updated, so the router still thinks its connected there.
It should not men much though.
None of that affects local access. There is a bigger issue.
Yeah that worked fine.
However, I can say that everything is now working as before.
What have I done?
Just disconnected the LAN ports once and reconnected them. The assignment of the ports and the IP is identical, as I already had a static IP for Unraid and HA before. But although no changes are visible for mer, I can now reach HA via all three paths again: IP, local address and Duck DNS.
Perhaps my unconventional solution will help others with the changeover. Thanks for your time and help!