Marouen Dbouba

same error here.

I always got the error: **"[eth] =✘= Web3 connection attempt #0 failed"** this my app.json : ``` [ { "name" : "node-app", "script" : "app.js", "log_date_format" : "YYYY-MM-DD HH:mm Z",...

I run geth using this command line: `geth --datadir innofactory1/ --syncmode 'full' --port 30312 --rpc --rpcaddr 'localhost' --rpcport 8502 --rpcapi 'personal,db,eth,net,web3,txpool,miner' --bootnodes 'enode://20c47b4a7bd6d8383f87c1c988e601c7aa27ba7177b25d57e00794d1917c0c992dc37b93dfdf54741633179fd9a96a34fc2687d606ad48e2015ef2d958f3f0fb@10.2.1.124:30310' --networkid 1515 --gasprice '0' --unlock '0x40ee4953da28c4db0f15d671cefc29724ce2b87a' --password...

yeah isn't it enabled. but I am not sure "WS_SECRET" where to mention it in geth

sorry I made a typing mistake, I meant isn't enabled

@mattdawson but why node-rest-client depends on what user do with Array or Object prototype ?

@ledlamp I think to avoid those type of problems when we develop a library we shouldn't depends on user manipulations, thank's

OK.. but I was asking about ownership of data in the same database

thanks @coyotespike it works in CLI .. @haadcode Sorry for being late to give update

there is no updates yet?