You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to be able to have the browser js-ipfs code directly connect to a server that has a bit more stable and consistent connectivity. I also believe having this working is a prerequisite to getting pubsub to work between go-ipfs and js-ipfs, which I would eventually like to employ to push rapid updates to connected clients.
As part of the server functionality it includes a go-ipfs node that is needed to be running. The js-ipfs code in browser is capable of connecting to go-ipfs nodes via SECURE websocket due to the browser security model. The go-ipfs out of the box does not support TLS websocket. SOooooo we have to set up nginx as a reverse proxy on /wss path and proxy to the /ws path for the IPFS node. There are some guides out there, I will find more details and put here as I get closer to thinking about actually tackling this.
I believe the gist was
set up nginx in the docker
set up this nginx to get letsencrypt TLS cert
reverse proxy /wss to /ws on the IPFS node
ipfs node configuration has to enable the ws but adding some special thing in the config, which I can't recall
“/ip4/127.0.0.1/tcp/4003/ws" in the swarm list .... or something like that.
I would like to be able to have the browser js-ipfs code directly connect to a server that has a bit more stable and consistent connectivity. I also believe having this working is a prerequisite to getting pubsub to work between go-ipfs and js-ipfs, which I would eventually like to employ to push rapid updates to connected clients.
As part of the server functionality it includes a go-ipfs node that is needed to be running. The js-ipfs code in browser is capable of connecting to go-ipfs nodes via SECURE websocket due to the browser security model. The go-ipfs out of the box does not support TLS websocket. SOooooo we have to set up nginx as a reverse proxy on /wss path and proxy to the /ws path for the IPFS node. There are some guides out there, I will find more details and put here as I get closer to thinking about actually tackling this.
I believe the gist was
some more info:
ipfs/kubo#3907
ipfs/kubo#5251
The text was updated successfully, but these errors were encountered: