Quote from: profitofthegods on August 24, 2014, 02:11:17 PM

Quote from: profitofthegods on August 24, 2014, 01:33:46 PM

Quote from: SyRenity on August 24, 2014, 01:21:52 PM

Quote from: profitofthegods on August 24, 2014, 01:19:22 PM

Just tried this on AWS and the same thing happened as before - looks fine until I edit the config file then the log shows not synched and the web wallet becomes unreachable.

You just added password, and the node stopped working?

Please wait till until the wallet synced and try again, otherwise PM Boris (crypti) the logs..

Yes that is what happened.

Found this in the logs, could this be the problem?

Code:

{"level":"error","message":"Invalid payload length: 17075758229493073066 length: 496 buffer length: 440","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"info","message":"Crypti stopped!","timestamp":"2014-08-24T13:28:26.702Z"}
{"level":"error","message":"Error: Can't process block: 17075758229493073066","timestamp":"2014-08-24T13:28:26.702Z"}

Found the problem!

It doesn't like you editing files once its already running. I just started again from scratch but I edited the config file before running

Code:

sudo npm install -g forever

instead of afterwards as you have it in the instructions. Now I finally have

Forging Enabled!

Looks to be working from my end with Forging enabled.

Likewise, instead of restarting the node. I stopped, edited configuration file and then started the node.