I think this has been discussed before, but when Blue Iris server is auto updated and restarted, the Node Server stops working. A restart of the node server for Blue Iris fixes this. There was a solution to add code to possibly make it fix itself on a disconnect on a previous thread. I tried it, didn't seem to work (adding the suggested line makes the node server stay in disconnected state and won't connect). It appears this node server isn't actively being maintained. @bpwwer - I have seen you comment on others who would like the functionality of being able to restart a single node server either by a schedule or command line. I do understand your comments that it's just a band aid, but it would be nice to either have a real fix here, or this ability. You also indicated you are willing to help when the author might not be responsive or can't help (I believe the author here indicated they don't use Blue Iris anymore and can't test). Bottom line, any help here would be appreciated. I do code alot, I just don't use python, so I don't think I can easily figure out a solution . . . Thanks!

First off, my comments and reasons for not wanting to allow for automated restarts of node servers/PG3 are really because that tends to be used as a band-aid to handle poorly behaving node servers. The right way to do things is to get the node servers to not behave badly. In this case, the node server isn't really behaving badly, it's behaving mostly as intended. When it can't communicate with Blue Iris, it goes into a disconnected state and waits for someone to take action to resolve the issue. Now it could and should handle this better. It should try to re-connect, the code is mostly there, just not the logic to attempt that. In cases like this, where the author has pretty much abandoned the node server, I'll typically take a look if I have time. Unfortunately, I don't always have time to dig into someone else code to figure out how it works and what can be done to resolve any issues. You happened to ask at a time when I'm not real busy so I'm going to try and make some changes. Version 2.0.3 should try to re-connect when it fails to query the Blue Iris server. I have no way to test this.

Blue Iris Node Server Disconnected after Software update

Followers

November 23, 2024Nov 23

oops...I spoke too soon. I had not disabled by program that does a rediscover when a disconnect occurs. Just did test again and this time no automatic reconnect occurred. Still need to do a rediscover

9 months later...

September 12Sep 12

Is there anything further on this? Every time there is any hiccup in my network Blue Iris disconnects (despite saying "connected"). It seems that people are saying using the "re-discover" button will fix it. Do I need to just have a program that runs every hour triggering a "re-discover"?

2 months later...

1 hour ago1 hr

@bpwwer

I am still having issues with every time blue iris server restarts or otherwise goes down and then comes back online, the node server looses its connection and I have to manually restart it. I am not clear on if this has a programmatic solution or how to manage it.

Create an account or sign in to comment

Followers

Go to topic listing

Replies 27
Views 3.9k
Created 1 yr1 yr
Last Reply 1 hr1 hr

Sign In

Blue Iris Node Server Disconnected after Software update

Featured Replies

Create an account or sign in to comment

Top Posters In This Topic

Recently Browsing 1

Who's Online (See full list)

Forum Statistics

Account

Navigation

Search

Configure browser push notifications

Chrome (Android)

Chrome (Desktop)

Safari (iOS 16.4+)

Safari (macOS)

Edge (Android)

Edge (Desktop)

Firefox (Android)

Firefox (Desktop)