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
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?
The text was updated successfully, but these errors were encountered:
TheOneOgre
changed the title
Mesh settings bug
Mesh settings bug: AllowRequestForwarding determines state of itself and AcceptForwardedRequests
Jan 17, 2025
TheOneOgre
changed the title
Mesh settings bug: AllowRequestForwarding determines state of itself and AcceptForwardedRequests
Mesh settings: AllowRequestForwarding determines state of itself and AcceptForwardedRequests
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.
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:
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?
Thanks!
Discussed in #269
The text was updated successfully, but these errors were encountered: