-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
peers... #435
Comments
Ouisync tries to find peers automatically using one of the peer discovery mechanisms (Local Discovery, DHT, Peer Exchange). If none of them work for some reason, the user can add the peers manually by inputting their IP address and port. After the peer is discovered (or manually added), Ouisync will automatically try to connect to them. There is however a chance that this connection might fail, due to, for example, overly restrictive NAT or firewall settings. Perhaps that's what you are experiencing?
As I said, after the peer is discovered, we try to connect to them automatically. Adding a manual step to this would not improve the connection chance.
You only need to enter it once (assuming it doesn't change), as it is persisted across restarts. |
Yeah, I get it. The key thing is that after devices find each other, they just try to connect but nothing really happens. Even though they connect, after a few minutes syncing stops |
I manually added my devices in the peers tab under settings, and the files synced successfully.
(Of course, the Android 7 device had to be the rebel. all Files received corrupted, mission aborted. It's like the table knew. 🙄)
I've noticed that all the devices are visible to each other in the peers tab, but they seem to be stuck in a connecting status. Excuse me, but wouldn't it make sense to display active ouisynces by names in the network? I'm curious about the reasoning behind this approach. Perhaps we could consider allowing manual device selection if automatic connection isn't viable. It would save us from entering the IP and port repeatedly...
The text was updated successfully, but these errors were encountered: