HS4 shutting down every 5 minutes when Zerotier enabled.

[Traction Tim]

I installed Zerotier a couple of days ago. I set it up on my android mobile and on my BI5 pc. Using the Zerotier address as the WAN address on the phone worked well.

Next step was to install it on my HS4 server (Win11) and immediately I felt HS4 was running slow. Yesterday HS4 wouldn't accept commands, then it would and later it wouldn't. I checked the HS4 log to see it had rebooted. I searched back for the reason and found a graceful shutdown following a "Request from UI to shutdown". As I watched, I saw HS4 shutdown again and immediately reboot - OK, that's why it worked then didn't.

I filtered the log on "Request from UI to shutdown" and could see it had shut down almost every five minutes since I installed Zerotier. Stopped Zerotier and it didn't shut down. Started Zerotier again today (top two on the table) and HS4 shuts down after five minutes. OK, how accurate is that timing - export log to txt and stick it in Excel to calculate the delta:



OK, so fairly regularly 4:27 or 4:28.

Any ideas why this should work from my phone to my BI5 server (Win10) but not to my HS4 server (Win11) ? Why would Zerotier cause HS4 to shutdown ? And what is 4:27 ?

I need a drink

[pseudocode]

Is your machine rebooting or just HomeSeer restarting? If it's the machine then HomeSeer is irrelevant, but if not:

Possibly the "Request from UI" is misleading, as the shutdown script uses an HTTP call to request shutdown - so it may be the service/task is deliberately restarting.

Assuming it is just HomeSeer restarting, what are the log entries just before the shutdown?

As you're setting up a different network on the machine, it's possible that something is losing connectivity to HomeSeer and triggering the restart. Is there a watchdog script that could be doing that? I've done the same on my linux machine with Wireguard and it messed up several apps with circular routing and changing IP addresses.

[jon00]

Do you have HSSentry enabled? It polls the HS Web-server and if it cannot make contact, it will restart Homeseer. Sounds like the IP Address change is the issue.

[TC1]

HS4 has a bug in that losing network connectivity triggers a shutdown of HS4. I've raised this issue before, here is how I solved it. But you should read the entire thread:
https://forums.homeseer.com/forum/ho...48#post1507248

It seems that when ZeroTier is used it's transitioning between networks, ie, a local lan connection and a VPN-type connection. That would be similar to disconnecting the network temporarily.

Also, what Jon00 said.

[Traction Tim]

Hi all, it was just HS4 stopping and starting, not the pc. You wise people have hit the nail on the head - I went to read hs_sentry.log and found a lot of this happening at a time period I have seen before:

21/03/2023 18:05:54:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:06:16:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:06:16:Cannot access HomeSeer, shutting down system and re-starting...
21/03/2023 18:06:16:Killing HomeSeer HS4 application
21/03/2023 18:06:41:Starting the HomeSeer HS4 Application
21/03/2023 18:07:03:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:07:25:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:07:47:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:08:09:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:08:32:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:08:54:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:09:16:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:09:38:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:10:00:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:10:22:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:10:44:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:10:44:Cannot access HomeSeer, shutting down system and re-starting...
21/03/2023 18:10:44:Killing HomeSeer HS4 application
21/03/2023 18:11:09:Starting the HomeSeer HS4 Application
21/03/2023 18:11:31:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:11:53:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:12:15:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:12:37:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:12:59:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:13:21:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:13:43:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:14:05:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:14:27:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:14:49:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:15:11:Error accessing web server: Unable to connect to the remote server
21/03/2023 18:15:11:Cannot access HomeSeer, shutting down system and re-starting...
21/03/2023 18:15:11:Killing HomeSeer HS4 application
21/03/2023 18:15:36:Starting the HomeSeer HS4 Application

And it stopped logging it yesterday when I disabled Zerotier. OK, I may need a bigger hammer Time to turn a few things off.

[Traction Tim]

OK, HS_Sentry off has sorted it out for now. Zerotier is ON and HS4 is not crashing. I also noted I had IP binding set (I can't remember why as all of my server pc's have a static IP) with a local LAN IP in LABs, so I cleared that too. All appears normal on other pc's on my LAN. This has sorted out Owntracks MQTT from my Zerotiered phones too, so today is looking like a good day. No port forwarding any more. I hope Zerotier is as secure as it looks !

Thanks to all of you