2018-04-27 02:32:45.844 [API] WS_SECRET NOT SET!!!

[blockcloud]

When I start the project, it shows this and seems stopped. And I got a connection error when access localhost:3000.
What is the problem? Or how to find the error?

[zscole]

You need to run WP_SECRET=[your secret] npm start

…

Sent from my iPhone

On Apr 26, 2018, at 7:36 PM, blockcloud ***@***.***> wrote: When I start the project, it shows this and seems stopped. And I got a connection error when access localhost:3000. What is the problem? Or how to find the error? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[madhuri03]

giving error

[madhuri03]

From where I can generate WS secret?

[mikeyb]

read the error, has nothing to do with your WS_SECRET smh

[madhuri03]

error on console

How can I resolve this ?

[vingorius]

@madhuri03
Add your geth script "--ethstats Node1:Hello@localhost:3000".
Node1: node name
Hello: SECERT
localhost:3000: ethstats address

[jjhesk]

can just start with this line:

env WS_SECRET=111111 node app.js

[Keref]

Another way is to properly set the secret, by adding ws-secret.json in the eth-netstats directory, with
{ "ws_secret": "my_lil_secret" }

[daxdax89]

So how is this fixed on Windows?

[willtate]

@Keref Has it, but should be ws_secret.json