@ruslan_wing what are you using to test the connection? i'm also getting the same error on apothem that @redpill1 is showing... this worked without issue a week or so ago with our nodes.
Does anyone know if there are alternatives websockets for apothem that we can use while having this issue? Recently we were able to switch to an alternative RPC on blocksscan for apothem, but I haven't had luck finding an alternative wss.
Can you please try it now as i was able to connect thee apothem websocket with any issue
No, still getting similar errors.
0|2_nodeStartPM2 | 2022-07-06T13:14:59Z [DEBUG] eth.Client#Dial(...) eth/client.go:127 nodeName=eth-primary-0 nodeTier=primary wsuri=wss://ws.apothem.network
0|2_nodeStartPM2 | error starting app: websocket: bad handshake (HTTP status 200 OK)
@ruslan_wing what are you using to test the connection? i'm also getting the same error on apothem that @redpill1 is showing... this worked without issue a week or so ago with our nodes.
Does anyone know if there are alternatives websockets for apothem that we can use while having this issue? Recently we were able to switch to an alternative RPC on blocksscan for apothem, but I haven't had luck finding an alternative wss.
Hello
Hello,
Please use below RPC and WS for the apothem network.
rpc.apothem.network
wss://ws.apothem.network/ws