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
The discovery server could make connection tests to the announced addresses/ports and return the result to the client when it does the announcement. This could provide one small part of the "connection doctor" like functionality, in that Syncthing could display an indicator for success/failure.
In case of failure it could say something like Incoming connections on port 22000 blocked, check port forwards or firewall settings.
In case of success it can instead report the actual port used and that port forwarding works.
The test would have to be fairly "shallow" and use short timeouts, in order to not put too much extra work on the discovery servers. We need to plan on doing several hundred connection tests / second if we do this. We can skip checks on addresses that are reannounced and have succeeded within the last 24 hours or something.
The text was updated successfully, but these errors were encountered:
The discovery server could make connection tests to the announced addresses/ports and return the result to the client when it does the announcement. This could provide one small part of the "connection doctor" like functionality, in that Syncthing could display an indicator for success/failure.
In case of failure it could say something like
Incoming connections on port 22000 blocked, check port forwards or firewall settings
.In case of success it can instead report the actual port used and that port forwarding works.
The test would have to be fairly "shallow" and use short timeouts, in order to not put too much extra work on the discovery servers. We need to plan on doing several hundred connection tests / second if we do this. We can skip checks on addresses that are reannounced and have succeeded within the last 24 hours or something.
The text was updated successfully, but these errors were encountered: