-
Notifications
You must be signed in to change notification settings - Fork 13
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
How do we connect to a private remote substrate node? #3
Comments
Hello @noahsalvadordenjo I understand that you are trying to run a Substrate node on google cloud and connect the Polkadot JS Apps UI to it. There are a few ways to do this. I'll describe the easiest technique first, then a more robust technique. I'll also observe that getting the UI to connect is unrelated to telemetry. Using an Insecure Websocket (ws) When you run your node in google cloud you need to give it the # Run a dev node
./target/release/substrate --dev --ws-external
# Or in general
./path/to/substrate <your preferred flags> --ws-external Now that your web socket is open to the public, you can open your web browser. (Firefox will not work for this purpose because it will not allow an https site to connect to a ws websocket, work around this for now by using a different browser). You can navigate to https://polkadot.js.org/apps/#/settings. Enable the At this point you should be good to go. If you want to use firefox with the insecure websocket, you will need to host the Apps UI locally. Instructions for that are in its github repo. Firefox also works with the wss method (read on). Using a Secure Websocket (wss) If you are using this node for more than just playing around and learning, you'll eventually want a proper wss endpoint. To get one, you can use nginx on your server to act as a reverse proxy. You can reference the official docs and my notes for tips on setting this up and an example configuration file. When using a secure websocket, you no longer need |
Thanks a lot,
and connect polkadot with my external ip wss://35.223.179.7:9944 i still have the following error: |
The problem is that you specified the wrong endpoint. You wrote |
I've enabled my firewall port to allow al incoming traffic and i still have the following error |
Are you using firefox?
|
chrome |
Is it possible to change
to use my internal ip? |
I haven't seen that issue on chrome. It's possible that they have updated to the same policy as firefox. In that case you have two options.
|
Used the polkadot api locally and got the genesis hash! |
Dear substrate,
when I try to connect to my remote node on google cloud. using the telemetry-url ws://telemetry.polkadot.io:1024
Polkadot says "You are not connected to a node. Ensure that your node is running and that the Websocket endpoint is reachable."
How do i set up a secure/insecure websocket endpoint on substrate?
And when i try to connect to the following endpoint
"/ip4/35.223.179.7/tcp/30333/p2p/QmVNEAoh4TFLX2
cNEGogv3Gy8vBHw5ATU7biZYpsdwA14t"
polkadot says the same
I've read the following:
https://wiki.polkadot.network/docs/en/maintain-wss
when i try to setup the nginx server and the server asks me for a domain name: I enter "http://nachtstein.nl""
i get the following error:
Does anyone know a good tutorial?
The text was updated successfully, but these errors were encountered: