apothem websocket error

Any idea if apothem websocket is working fine? wss://ws.apothem.network
It was working fine, and all of a sudden seeing this error (and few others are also reporting the same issue).
"error calling getEthBalance on Ethereum node: primary websocket (wss://ws.apothem.network) call failed: websocket: bad handshake (HTTP status 200 OK)"

Discussion (11)

samsam • Jul 8 '22 • Edited on Jul 8

@akhekade @riteshkakkad where can we get quick help for developers on XDC network? apothem network websocket is practically not working for several people, but I cannot get help on Telegram and was asked to come over here, but we still don't have apothem websocket working after 2-3 days. Is this the best we can expect from XDC Network for developers coming onboard? Sorry, it is an honest question. Thanks

AnilChinchawale • Jul 8 '22

Hello,

Kindly use below RPC and WS for apothem network.

rpc.apothem.network
wss://ws.apothem.network/ws

samsam • Jul 8 '22

Thank you Anil, appreciate that. Now it seems to be working fine, and we can start using for tests and let you know if we run into any issues. Thanks again.

Atul Khekade • Jul 8 '22

If comment by @anilchinchawale below, does not resolve the issue, please tag me back in the same article. We have asked alternative infra providers to set this up as well.

samsam • Jul 8 '22

Thanks Atul, really appreciate that. We have high hopes for XDC Network to be top, if not The Top blockchain. It is just no brainer, seeing so many struggles and failing projects on Ethereum because of fees and speed severe constraints, and in comparison XDC Network's near-zero fees and speed of finality etc.
Keep up the great work.
PS: Yes, onboarding Ethereum DEVs swiftly and some marketing push to lure them to build more projects on XDC would take it a long way sooner. My two cents.

Ritesh kakkad • Jul 16 '22

Open source code and process to setup dedicate websocket available at : github.com/xinfinorg/XinFin-Node

please try to setup and let us know feedback with any issue.

ruslan wing • Jul 6 '22

Can you please try it now as i was able to connect thee apothem websocket with any issue

samsam • Jul 6 '22 • Edited on Jul 6

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)

go140point6 • Jul 6 '22

@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.