Web3 connection attempt failed about eth-net-intelligence-api HOT 19 OPEN

I had the same issue and on checking further in the source code, I saw that the values that were being specified in the app.json file were not being taken into consideration. The following worked for me:

RPC_HOST=server_ip RPC_PORT=port_here WS_SERVER=ws_server_here WS_SECRET=secret_key node app.js

This solved the problem and connected to my local node

from eth-net-intelligence-api.

magically started working now :)

from eth-net-intelligence-api.

I have the same issue after updating netstats, unfortunately magic hasn't started working for me yet..

from eth-net-intelligence-api.

Had similar issue when ethereum was not running with rpc enabled. With geth:

geth --rpc

I updated the wiki

from eth-net-intelligence-api.

Thanks!

I just wanted to check my node and yes, I had --rpc enabled already but even better, somehow it fixed itself, seems magic did the trick for me!

from eth-net-intelligence-api.

gotcha, needed to run node 0.12 instead of 5.10 (or at least any lower version)

from eth-net-intelligence-api.

I have the same problem and not solve with rpc enabled.

• I runnig geth wtih this parrams:
  --rpcaddr localhost --rpc --rpcport 8545 (I trying also rpcaddr 0.0.0.0)
• my app.json:
  {
  "NODE_ENV" : "production",
  "RPC_HOST" : "localhost",
  "RPC_PORT" : "8545",
  "LISTENING_PORT" : "30303",
  "INSTANCE_NAME" : "geth",
  "CONTACT_DETAILS" : "",
  "WS_SERVER" : "http://localhost:3000",
  "WS_SECRET" : "",
  "VERBOSITY" : 2
  }
• open inteligence api:
  pm2 start app.json
• open netstats:
  PORT=3000 WS_SECRET=npm start
• Error:
  [eth] =✘= Web3 connection attempt #0 failed

versions:
geth: 1.4.5
node: 0.12

from eth-net-intelligence-api.

Same problem.
I use Parity, and I get Web3 connection attempt #1 failed when I use the --jsonrpc-interface 0.0.0.0 option.

from eth-net-intelligence-api.

I'm also having this problem.
Why is this closed?

from eth-net-intelligence-api.

Same Issue Here.

from eth-net-intelligence-api.

well is the service listening? If it cant connect, its probably not running. Make it run and I bet you can connect. $5 says misconfiguration, try the docs again

from eth-net-intelligence-api.

I delete it all and redo again... it works.
Don't know where the problem was, but at least it works now.

from eth-net-intelligence-api.

Similar issue here, my web3 connection from eth-netstats fails despite that node is running normally with the following arguments:

geth --nodiscover --bootnodes enode://83faad28b4bd3cbf6fc2245a4f95ab9b068c30fd0b9972a4042aa5afe21128d2989e5cb6791e0193c5ed139fce41688a6ddceb9464a8fb155254ef0d112ececa@<bleh>:30303 --networkid 14 --rpc --rpcaddr "0.0.0.0" --rpccorsdomain "*" --rpcapi web3,eth,net,db,personal,miner,admin,debug --fast

I can connect from any machine using:

geth attach http://<bleh>:8545/

And can use all of the enabled apis. Any ideas?

from eth-net-intelligence-api.

Experiencing the same problem, using docker, have any solutions occurred?

from eth-net-intelligence-api.

Adding the --rpc worked for me, was using docker and k8s

from eth-net-intelligence-api.

@suyash515 great catch. I too was experiencing this problem and your comment saved me a lot of headache +1.

from eth-net-intelligence-api.

same error here.

from eth-net-intelligence-api.

@suyash515 +1 as well. Surprised that there hasn't been an update to this yet? Otherwise a super cool tool. Probably could also use some sort of log-level option; theres a ton of output from the tool that makes doing other work on the instance difficult

from eth-net-intelligence-api.

Hello @phoax
Were you able to run using Parity before?
When I am using infura, I am getting erros like

[eth] xx> getLatestBlock couldn't fetch block...

[eth] xx> Error: invalid argument 0: empty hex string

Any advice will be helpful, thank you

from eth-net-intelligence-api.