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

not connecting anymore #65

Open
Head opened this issue Aug 28, 2016 · 7 comments
Open

not connecting anymore #65

Head opened this issue Aug 28, 2016 · 7 comments

Comments

@Head
Copy link
Contributor

Head commented Aug 28, 2016

See screenshot. After the latest npm install the bridge/everything is not working anymore:

unbenannt

@mappum
Copy link
Owner

mappum commented Aug 28, 2016

Hm, nothing there should have changed. Thanks for the heads up, I'll check it out.

@Head
Copy link
Contributor Author

Head commented Aug 31, 2016

\npm\node_modules\webcoin-bridge\node_modules\bitcoin-net\lib\bridge.js:30
return (_this2 = _this)._selectPeer.apply(_this2, arguments);
^

TypeError: Cannot read property 'apply' of undefined
at Peer.selectPeer (\npm\node_modules\webcoin-bridge\node_modules\bitcoin-net\lib\bridge.js:30:42)
at Peer._onGetPeer (\npm\node_modules\webcoin-bridge\node_modules\peer-exchange\lib\peer.js:268:8)
at emitOne (events.js:96:13)
at emit (events.js:188:7)
at . (\npm\node_modules\webcoin-bridge\node_modules\peer-exchange\lib\peer.js:92:36)
at emitOne (events.js:96:13)
at emit (events.js:188:7)
at readableAddChunk (\npm\node_modules\webcoin-bridge\node_modules\readable-stream\lib_stream_readable.js:198:18)
at Readable.push (\npm\node_modules\webcoin-bridge\node_modules\readable-stream\lib_stream_readable.js:157:10)
at Duplexify._forward (\npm\node_modules\webcoin-bridge\node_modules\duplexify\index.js:162:26)

@Head
Copy link
Contributor Author

Head commented Aug 31, 2016

Yep, the [email protected] works. I have to install the bridge 1.3.0 with bitcoin-net 4.3.2 and delete the bitcoin-net folder in the bridge/nodue_modules. Then it works again.

It seems like your testnet webSeeds are all down too. They don't respond in http://websocket.org/echo.html

@mappum
Copy link
Owner

mappum commented Aug 31, 2016

I think the Let's Encrypt certs expired, and that crashed them. I started rewriting peer-exchange yesterday to better handle relaying to TCP nodes, I expect to publish it today. I'll renew the certificates and put the webseeds back up.

Would you be interested in running a web seed? It would be nice to have the ownership of them less centralized. It only really needs bandwidth, it could run on a $5 VPS.

@mappum
Copy link
Owner

mappum commented Aug 31, 2016

Oh, you said it is working with 0.5.3? Hm, I'm not sure how you can connect to the webseeds seeing as the certs have expired.

@Head
Copy link
Contributor Author

Head commented Sep 1, 2016

5.3 with my local node.
I'm not sure. The crash above is also the local one, without a cert.
It's hard for me to debug what exactly happens because I'm new to nodejs. Worked 15 years with PHP...

I could setup one if I find a decent hoster for node. What exactly do they do? They bridge all traffic from the clients to the Bitcoin nodes? Or do the webclients connect to other clients?

@mappum
Copy link
Owner

mappum commented Sep 1, 2016

Ah, I never looked at your crash stack trace, the problem is coming from some changes I made a while ago in peer-exchange which I'm unhappy with, hence the rewrite. Migrating to the new version once it's ready will fix this.

Worked 15 years with PHP...

😮 Wow! I didn't even know PHP was 15 years old.

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

2 participants