Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Can't connect p2p (windows)

See original GitHub issue

When I try to connect to a remote peer I get:

Dat could not find any connections for that link.
There may not be any sources online.

dat doctor is returning only Trying to connect to xx.xx.xx.xx

Tried Windows 10 and Ubuntu subsystem for Windows.

Any ideas?

Issue Analytics

State:
Created 6 years ago
Comments:5

Top GitHub Comments

2reactions

joehandcommented, Oct 19, 2017

UTP is now supported on windows! Please reinstall to update the dependencies.

0reactions

pfrazeecommented, Jun 20, 2017

Realistically speaking, I doubt that TCP will connect to anything except for peers that are running on servers

On Tue, Jun 20, 2017 at 12:46 PM, Joe Hand notifications@github.com wrote:

Does that effectively mean we can’t signal in p2p mode?

Maybe, we use UTP to get around firewalls or otherwise inaccessible networks. If you are able to open a port for dat you should be able to connect p2p easier. By default, dat uses 3282 port but you can pass other ports to any command: dat share --port 61123.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/datproject/dat/issues/809#issuecomment-309835262, or mute the thread https://github.com/notifications/unsubscribe-auth/ABNhU6dFChdyKjahe_tVkRERhjycRUh6ks5sGAVvgaJpZM4N-x65 .