Skip to content
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

Cannot publish a dat, doctor command is missing, any ports should I forward to me? #1184

Open
brailateo opened this issue Apr 16, 2020 · 6 comments

Comments

@brailateo
Copy link

Watching DatProject for 2 years, still I'm waiting for some great news! :-(

Tested 14.0.2 version on a Linux Ubuntu 18.04 x64 machine!
First of all: doctor command is not found:

$ .dat/releases/dat-14.0.2-linux-x64/dat doctor

all I get is the help!

Tried last DatDesktop app. Published a DAT folder here ... tried to access it there , both computers under home wifi routers. Didn't worked!
Tried Doctor command inside DatDesktop.
It keeps saying

[info] Testing connection to public peer
[error] FAIL - unable to load utp-native, utp connections will not work
[info] TCP ONLY - success!
[info] End of phase one (Public Server), moving on to phase two (Peer to Peer via DNS)
[error] Could not detect public ip / port

Searched the docs for any ports that I should open and forward from the router to my machine!
Didn't find anything at all! :-(

Tried demos from hyperswarm (I understood that Dat is using that).
PEER DISCOVERY WORKED, EXACTLY BETWEEN THOSE 2 MACHINES I'VE TESTED WITH DATDESKTOP!

Anything more I should do?
I was abandoning any projects with IPFS when I saw that it cannot publish something to the world when behind NAT routers.
I hope that DAT will do that!

Teo

@okdistribute
Copy link
Collaborator

okdistribute commented Apr 16, 2020

Hi Teo, Please try npm install -g dat@next!

@brailateo
Copy link
Author

brailateo commented Apr 16, 2020

teo@amd:~$ dat-doctor
Welcome to Dat Doctor!

Software Info:
  linux x64
  Node v12.16.2
  Dat Doctor v2.1.2

Running Basic Tests (Checks your Dat installation and network setup)

✖ Who am I?
    ERROR: Could not detect public ip / port
✔ Loaded native modules
✔ Resolved Dat Doctor Server
✔ Successful data transfer with Dat Doctor via TCP
✔ Successful data transfer with Dat Doctor via UDP

FAIL
4 of 5 tests passed

Your network may be preventing you from using Dat.

Is there any port I should open on my router to forward directory to my computer?

@brailateo
Copy link
Author

dat-doctor is giving the same error:

✖ Who am I?
    ERROR: Could not detect public ip / port

even on a server with public IP address! :-(
Teo

@okdistribute
Copy link
Collaborator

@brailateo dat-doctor is deprecated, that's why it is removed from npm install -g dat@next

@brailateo
Copy link
Author

@okdistribute OK, good to know! :-) I hope that it should be removed from all docs, it confuses people!
So the next question is "Dat Desktop is in sync with dat@next?"
Because the last time I tried a sync I used "Dat Desktop", I give it another try!

Test 1
I tried right now with dat 14.0.2 used at command line, to publish (behind a home router) a dat, cannot clone on the other side, even on a server with public addres. :-(

Test 2
Tried publishing from the server with public address and cloning on the desktop behind the home router. It worked! :-)

So, the last question is:

Is (or would it be) able dat to sync directories from any computer behind home routers directly, with STUN like coordination or through DAT nodes relaying (or TURN), like in WebRTC video chat. without forwarding ports from the routers?

Thanks for your help!
Teo

@decentral1se
Copy link

So the next question is "Dat Desktop is in sync with dat@next?"

Please see dat-ecosystem-archive/dat-desktop#648.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants