Open lesnikutsa opened 1 year ago
Most often this is caused by a proxy, like nginx, not being configured to handle websockets.
Specifically for nginx it looks something like:
location /ws {
proxy_pass http://127.0.0.1:8888/ws;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_set_header Host $host;
}
I noticed that when we specify an RPC node in the format https://m-jackal.rpc.utsa.tech:443 (namely https), we often have connection problems But when we specify RPC in the format http://65.108.6.45:60857/ (http) we have no problem and we connect right away. Will this be resolved in future updates?