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
{{ message }}
This repository was archived by the owner on Nov 15, 2023. It is now read-only.
I am unable to access my node though the polkadot-ui if I attempt to set "--rpc-cors" to anything but "all".
Starting from scratch and without any "--rpc-cors" configured, when I attempt to access the node, in the log I get: "Blocked connection to WebSockets server from untrusted origin: Some("https://1.2.3.4:8080")"
Fine, so I add the following string and try again: "--rpc-cors "https://1.2.3.4:8080""
There's progress, I am now asked for a different cors string: "Blocked connection to WebSockets server with untrusted host: Some("1.2.3.4")"
At which point I am getting the same exact error logged: "Blocked connection to WebSockets server with untrusted host: Some("1.2.3.4")"
I am accessing my Kusama node through a Wireguard VPN, where the node is behind a nginx instance. Locally (MacOS / Brave), I use the polkadot-ui interface hosted on IPFS (https://polkadot.js.org/apps/ipfs/).
Again, it is working perfectly fine with "--rpc-cors all". At this point I am simply trying to tie loose ends and make sure my security is as solid as it can be, ready for Polkadot.