Jump to content

[2.2.1] Node.js Disconnecting Again?

GrooveOnBeat

By GrooveOnBeat

    • Babble 2.2.1 Closed Bug
 Share

After entering a single message it disconnects, and browser doesn't matter. Even if firewall is disabled.

The private key in the ACP and babble.js are the same. 

forever start /home/site/public_html/forums/applications/babble/sources/Node/babble.js

The output show 

warn:    --minUptime not set. Defaulting to: 1000ms
warn:    --spinSleepTime not set. Your script will exit if it does not stay up for at least 1000ms
info:    Forever processing file: /home/site/public_html/forums/applications/babble/sources/Node/babble.js

Is there a way to kill the process and then restart?

I've tried:

forever stop
forever restart
 

 

 Share
Go to entries

User Feedback

Recommended Comments

Michael

might be a settings store issue. if you aren't getting the "babble is disconnected" message when first going to it, its most likely the validation is failing.

run the support tool in ACP->System->Support to the first stage

Quote

Sometimes badly cached data can cause problems. We have cleared all cached data, please check and see if your problem has been resolved.

you'll get the following message when the data store has been cleared.

if that fails, try  remove the secret key, click save (it will generate a new one, and if it has write permissions it will update the babble.js) then restart the babble.js in forever. 

Link to comment
Share on other sites
GrooveOnBeat

I hope I'm not jumping ahead but that sequence may have worked! Thanks! xD

Support then removed and generated a new private key, then restarted babble.js. When I used "forever restart" I tagged the id which I found in "forever list".

"forever restart id"

I'll update just to be sure.

 

Link to comment
Share on other sites

×
×
  • Create New...