We have a geth node setup. We can call the json rpc (through a tunnel), e.g. posting:



"jsonrpc": "2.0",
"id": 1,
"eth": "1.0",
"net": "1.0",
"rpc": "1.0",
"web3": "1.0"

The devs are saying the web3 api is not working. How can I test this with curl or socket tester or similar?

We are starting it thushly:

/usr/bin/geth --syncmode fast --cache=4096 --rpc --ws --wsorigins * --wsapi web3 --datadir /mnt/eth_volume 2>/var/log/geth.log

And hitting it on the standard ports (8545/8546) through a tunnel.

If I try with chrome websocket client on 8546, I always get connection refused, although the RPC test client on 8545 works.

  • The devs are saying the web3 api is not working - please elaborate on attempts made by "the devs". – goodvibration Jul 10 '18 at 13:34

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.