You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Mesh settings: AllowRequestForwarding determines state of itself and AcceptForwardedRequests #270
I have 2 servers running in mesh with each other, and while they do occasionally send requests to each other, the mesh json configuration seems to not be applying properly, specifically "AcceptForwardedRequests" and "AllowRequestForwarding"
For one, I tried following exactly what the documentation says:
An example would be a Raspberry Pi and a Macbook Pro. The Pi might have AcceptForwardedRequests false and AllowRequestForwarding true, and the mac could have AcceptForwardedRequests true and AllowRequestForwarding as false. This provides the Pi with help if needed, without worrying about the mac sending unwanted load.
So on my primary server with the GPU (which I prefer requests go to), AcceptForwardedRequests is true and AllowRequestForwarding false. This actually breaks mesh as, in the Mesh tab, it shows that the server will not accept or forward requests. Changing AllowRequestForwarding to true, reenables the acceptance, but also reenables forwarding.
On the second server, AcceptForwardedRequests is false and AllowRequestForwarding true, but this shows as both it accepting and sending requests. So same kinda issue but backwards. It seems, at least, the value of AllowRequestForwarding is determining the status of AcceptForwardedRequests as well.
Have tested it on fresh installs and the same behavior happens. The requests are getting forwarded however occasionally.
Also, is there any option like PreferMeshServer to have the primary server be preferred for processing and only fallback when it is unreachable?
changed the title [-]Mesh settings bug[/-][+]Mesh settings bug: AllowRequestForwarding determines state of itself and AcceptForwardedRequests [/+]on Jan 17, 2025
changed the title [-]Mesh settings bug: AllowRequestForwarding determines state of itself and AcceptForwardedRequests [/-][+]Mesh settings: AllowRequestForwarding determines state of itself and AcceptForwardedRequests [/+]on Jan 17, 2025
I followed that example below also
An example would be a Raspberry Pi and a Macbook Pro. The Pi might have AcceptForwardedRequests false and AllowRequestForwarding true, and the mac could have AcceptForwardedRequests true and AllowRequestForwarding as false. This provides the Pi with help if needed, without worrying about the mac sending unwanted load.
Seems like this is abandon-ware now. I've stopped using it and moved away due to numerous issues cropping up with newer releases of Blue Iris, and much better efficiency using other programs anyways.
Well mine still working doesn't lockup on Blue Iris 6.0.0.1. Kind of stuck with it as have 2 dual Coral TPU punning. What could you recommend for AI that can run 2 dual Coral TPU,s
Well mine still working doesn't lockup on Blue Iris 6.0.0.1. Kind of stuck with it as have 2 dual Coral TPU punning. What could you recommend for AI that can run 2 dual Coral TPU,s
Actually, the main issue I was having was an extreme memory leak, but I was also using CUDA acceleration, so the problem may be entirely non existent since you're using a Coral.
If it works, stick with it, I only moved initially because I had to.
Activity
[-]Mesh settings bug[/-][+]Mesh settings bug: AllowRequestForwarding determines state of itself and AcceptForwardedRequests [/+][-]Mesh settings bug: AllowRequestForwarding determines state of itself and AcceptForwardedRequests [/-][+]Mesh settings: AllowRequestForwarding determines state of itself and AcceptForwardedRequests [/+]cgserrant commentedon Jan 28, 2025
I followed that example below also
An example would be a Raspberry Pi and a Macbook Pro. The Pi might have AcceptForwardedRequests false and AllowRequestForwarding true, and the mac could have AcceptForwardedRequests true and AllowRequestForwarding as false. This provides the Pi with help if needed, without worrying about the mac sending unwanted load.
And result was
TheOneOgre commentedon Dec 17, 2025
Seems like this is abandon-ware now. I've stopped using it and moved away due to numerous issues cropping up with newer releases of Blue Iris, and much better efficiency using other programs anyways.
cgserrant commentedon Dec 17, 2025
Well mine still working doesn't lockup on Blue Iris 6.0.0.1. Kind of stuck with it as have 2 dual Coral TPU punning. What could you recommend for AI that can run 2 dual Coral TPU,s
TheOneOgre commentedon Dec 17, 2025
Actually, the main issue I was having was an extreme memory leak, but I was also using CUDA acceleration, so the problem may be entirely non existent since you're using a Coral.
If it works, stick with it, I only moved initially because I had to.