could not connect to sbot -> challenge not accepted

semateos commented 6 years ago

I have Patchwork running on my mac desktop, tried to put a fresh install on my laptop (MacOS Sierra, Patchwork 3.8.6) and am getting the error "could not connect to sbot" with every pub in the getting started list. Dev tools shows the message "challenge not accepted" (see attachment). I can connect to friends on the local network so sbot appears to be running correctly. But for some reason can't connect to any pubs. Any ideas? Thanks!

semateos commented 6 years ago

I tried again yesterday at home with a couple pubs and it didn't work (same errors as before). I just tried again now using an invite from http://ssb.hypersignal.xyz/ and it DID work. So seems like an intermittent kind of issue. Those are always super fun to track down. Happy to help if I can.

Happy0 commented 6 years ago

I've seen similar issues where a pub is intermittently not responding to requests to redeem an invite, but then if you retry, it does respond. However, although patchwork follows the pub (on redeeming the invite) and your client receives some gossiped messages (at least, I think my friend's client did), the pub does not follow you back.

I'd like to:

Make it clear when posting on patchwork with no followers that nobody will see your post, and you should try following another pub and making sure it follows you back.
Track down the issue with the scuttlebot instance not following back and see if we can only complete the invite operation once it has followed back.. Or something. Perhaps the instance is simply too busy with other tasks.

I just had this issue when using an invite code from ssb.exitsystemcall.com so that a new person could see my reply to them.

semateos commented 6 years ago

Yeah, I'm wondering if we can get a sense from those pub owners about how much load they're seeing. I tried all of them multiple times, consistently saw that error, and there was no aspect of the connection working (I was not downloading any messages). But then my attempt at 2am worked - which could maybe point to load on the pubs. It would be a good problem to have in a way, meaning the network is getting enough use to put a strain on all of those pubs... if that's the case, one thought for the short term would be to expand the list of pubs on the getting started page - there must be more reasonably stable pubs running out there - and could maybe randomize the order so new people are less clumped up...

nsantini commented 6 years ago

The same happening to me, trying to access any of the pubs listed on the public pub list...

brylie commented 6 years ago

I am having the same problem with the Linux AppImage.

Firstly, most of the public hubs seem to be offline, or at least it is hard to find out how to get an invite.

screenshot_20180422_115735

That aside, when I did manage to get an invite from https://ssb-pub.solvingmaz.es/ I get the could not connect to sbot error:

screenshot_20180422_115849

simonv3 commented 6 years ago

To elaborate on that (I used https://ssb.nz which loaded, nothing else did), using AppImage on ubuntu 18.04 I get this in the console:

connect ECONNREFUSED : "Error: connect ECONNREFUSED : at Object.exports._errnoException (util.js:1024:11) at exports._exceptionWithHostPort (util.js:1047:20) at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1150:14)"

How AppImage works is a bit of a mystery to me, but I can try and help debut.

Edit: restarting Patchwork seems to have worked. I can connect to diefreien.club.

polynomialherder commented 6 years ago

I was having this issue with my own pub hosted remotely on Digital Ocean that I was trying to connect to with Patchwork running via npm start on my local machine.

In my case it ended up being because my Digital Ocean droplet's firewall was permitting UDP and DNS connections from my local IPv6 address but not my local IPv4 address. When I added the IPv4 address I was able to connect without issue.

stale[bot] commented 6 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

roberto68 commented 5 years ago

I am getting this error on @3.11.0 installed via npm full error Error: could not connect to sbot at /home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/ssb-client/client.js:70:23 at next (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/multiserver/compose.js:24:14) at /home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/multiserver/compose.js:34:9 at _cb (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/multiserver/plugins/shs.js:28:20) at /home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/secret-handshake/protocol.js:117:22 at /home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/pull-handshake/index.js:10:5 at /home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/pull-handshake/index.js:23:13 at callback (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/pull-pushable/index.js:81:7) at drain (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/pull-pushable/index.js:68:39) Error: shs.client: server hung up when we sent hello (phase 3). Possibly we dailed a wrong number, or the server does not wish to talk to us. at abort (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/secret-handshake/protocol.js:37:45) at Object.cb (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/secret-handshake/protocol.js:52:26) at drain (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/pull-reader/index.js:43:23) Error: stream ended with:64 but wanted:80 at drain (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/pull-reader/index.js:43:26) at /home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/pull-reader/index.js:63:18 at /home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/pull-reader/index.js:20:7 at drain (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/stream-to-pull-stream/index.js:126:18) at Socket.<anonymous> (/home/roberto/.nvm/versions/node/v10.15.1/lib/node_modules/git-ssb/node_modules/stream-to-pull-stream/index.js:147:5) at Socket.emit (events.js:194:15) at TCP._handle.close (net.js:600:12) ssb-friends: stream legacy api used ssb-friends: get legacy api used { message: 'not a valid address:{"host":"usw.ssbpeer.net","port":8008,"key":"@MauI+NQ1dOg4Eo5NPs4OKxVQgWXMjlp5pjQ87CdRJtQ=.ed25519"}', name: 'Error', stack: 'Error: not a valid address:{"host":"usw.ssbpeer.net","port":8008,"key":"@MauI+NQ1dOg4Eo5NPs4OKxVQgWXMjlp5pjQ87CdRJtQ=.ed25519"}\n at Object.<anonymous> (/home/roberto/bin/patchwork/node_modules/@staltz/sbot-gossip/index.js:276:21)\n at apply (/home/roberto/bin/patchwork/node_modules/muxrpc-validation/index.js:173:15)\n at Object.add (/home/roberto/bin/patchwork/node_modules/muxrpc-validation/index.js:62:14)\n at Object.<anonymous> (/home/roberto/bin/patchwork/node_modules/@staltz/sbot-gossip/index.js:217:16)\n at apply (/home/roberto/bin/patchwork/node_modules/muxrpc-validation/index.js:173:15)\n at Object.<anonymous> (/home/roberto/bin/patchwork/node_modules/muxrpc-validation/index.js:82:14)\n at Object.hooked (/home/roberto/bin/patchwork/node_modules/hoox/index.js:10:15)\n at Object.localCall (/home/roberto/bin/patchwork/node_modules/muxrpc/local-api.js:31:29)\n at Object.<anonymous> (/home/roberto/bin/patchwork/node_modules/muxrpc/local-api.js:37:22)\n at Object.request (/home/roberto/bin/patchwork/node_modules/muxrpc/stream.js:46:17)' } Error: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

ssbc / patchwork

could not connect to sbot -> challenge not accepted #738