Closed gil-air-may closed 5 years ago
@gil-air-may go-ipfs doesn't have webrtc discovery or transport so you'll not be able to connect to it in this way.
It does have a websockets transport though so you should be able to connect and use pubsub with it. The "exchange files in browser" example should help you set this up:
https://github.com/ipfs/js-ipfs/tree/master/examples/exchange-files-in-browser
Type: Question
Description:
I'm having difficulty using pubsub between a browser node (using js-ipfs) and a go-ipfs node running on my machine.
First, I tried to setup a direct connection between the nodes, but I keep getting the same error:
Since this was not possible, I attempted to setup a p2p connection between Node A and B. I believe this was done correctly. The browser logs:
Despite having set up the p2p circuit, the node running on my machine does not receive the message published by the node running on the browser.
Steps to reproduce the error:
I start the daemon on the terminal using:
ipfs daemon --enable-pubsub-experiment
and subscribe to the topic usingipfs pubsub sub testing123
I instantiate the node on the browser using:
I navigate to localhost:3000 and the console logs:
Then on the browser, we try to communicate with the daemon using
After this, browser console logs:
published to testing123
but the daemon does not get the message. :cry:Question
I would like to know if it is possible to get the Pubsub functionality working between these two types of nodes. If so, I was hoping someone could point me in the right configuration for both nodes. The current configuration for both nodes can be found here:
https://github.com/open-science-org/idea-hub/issues/10
Thanks!