Here is what you should see:
==> telnet 192.168.1.137 8123
Trying 192.168.1.137…
Connected to 192.168.1.137.
Escape character is ‘^]’.
^CConnection closed by foreign host
It connects but but HA closed the connection
Did you alter the port on NUC2 during the process?
8193 is not 8123, saw the already in the initial post in step 11, but I looked like a typo. But here you are using port 8193 in the telnet command?
Armin
No. Mostly a typo or copy-paste from an original typo. In post 11, the 8193 is definitely a typo. It should read www://homeassistant.local:8123, and port 8123 is the port forwarded in my router (post 12).
I don’t normally use telnet, but I ran the test that @timj.pdx recommended. Also telnet to port 8123 failed.
I set my static and permanent, and when I do the backup it pulls in the IP I want.
i do this for a couple of reasons:
- I can always remember what it is, and it makes it easier later when you are connecting it to other items
- From my experience DNS is a finicky beast. If I can set a static IP then the name-IP DNS entries are not as disturbed, and I do not have to run around flushing DNS to find a system with the same name.
That would be option 1 from above. It would really up to you if you do a couple steps before Step 1 of setting a Static IP, and then redoing your backup.
I hope you are back up and running. My apologies, but I started down a path of MQTT, Blue Iris and motion events last night myself and haven’t finalized that.
I do appreciate your inputs. I would not have thought of looking at the IP distribution until possibly going down the wrong rabbit hole too far to get out.
I am running into a new problem- full backup is failing because of a missing file in the Media directory. But that will be in another thread.
1 Like
Marked as the solution.
The fix was remarkably simple and I am posting this for anyone else who has a similar issue.
Background:
My Home Assistant installation was on an Intel Nuc8i3. Worked great for the past three years. However, in the past couple of weeks the host has been crashing. Once or twice a day, sometimes two days between crashes. The terminal on the NUC was indicating what looked like a memory or SSD issue.
My proposed solution:
I have an identical Intel NUC8i3 that was not used often, so I thought, just install HAOS to NUC2 then restore the last backup from NUC1. I had performed restores before with no issues, and I had advised people moving to a new host to do the same. I thought I was in good company.
The problem:
I was unable to connect a browser to Home Assistant running on NUC2. Nothing worked. HA on NUC2 worked fine until the restore. The Home Assistant CLI on NUC2 worked fine. The Home Assistant Observer on port 4357 said everything was fine. Even automations and Node-RED flows were working.
The solution:
@reotto posted a question that pointed me to the problem. I am not a fan of static IP addresses, preferring to let the router make fixed IP assignments. With almost 100 devices, the router manages a few fixed IP addresses (permanent leases) and the remainder by DHCP. Both of the NUCs had fixed IP addresses in the router, so on boot NUC2 was getting it’s IP as 192.168.1.54, but all of the configurations in the restored Home Assistant was expecting the host to be at 192.168.1.57. The solution was to simply reassign the NUC2 fixed IP assignment to 192.168.1.57.
Problem solved.
Home Assistant is running on NUC2 and I can take my time analyzing why NUC1 was crashing.
Thank you to all who offered thoughts toward fixing my issue.
3 Likes