Jot server - SOLVED

SOLVED

Hi guys

Strange thing discovered. Here in chronological order:

1. There is working  site with working (3 mo long) Jot. In this time no changes was applied except app's upgrading.

2. Eventually downtime host server a couple days ago

3. Unable to Connect  Jot after server go up

4. Reboot host server. Unable to Connect  Jot

5. run "forever app.js" in Jot server folder on server. As result Jot is connected

BUT

6. Jot agree to work as long as SHH console is open! When I close SSH console window and disconnect SSH connection to server - it interrupts connection for Jot on site and I start to see The Lonely Black Plug trying to find his One And Only Socket :))

..............

here the SSH console dialog:

admin@myserver.com [~/public_html/jotsrv]# forever app.js
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
primus:
primus: We've detected that you're using a HTTP instead of a HTTPS server.
primus: Please be aware that real-time connections have less chance of being blocked
primus: by firewalls and anti-virus scanners if they are encrypted (using SSL). If
primus: you run your server behind a reverse and HTTPS terminating proxy ignore
primus: this message, if not, you've been warned.
primus:
forever app.js

.............

Any suggestions?

Thanx in advance

  • 628
  • More
Replies (10)
    • bump :)

      • bump #2

        • OK. 

          It was my mistake:  not forever app.js, it's need to run forever start app.js.

          I just leave it here for now.

          • Hello, 

            Yes, to start you should use - forever start app.js and for stop forever stop PID 

            • My jot messenger has not been able to connect, it hangs on connecting.... My certificate is and has been valid, will there be a fix for this?

              • Hello Will Monte,

                You need to restart Jot Server: login via SSH to the server and then go to jot server directory. 

                Here you need perform two commands:

                first this one:

                forever stop app.js

                and then 

                forever start app.js

                Now server should work fine again. 

                If any problems, contact me via PM please, I will help.

                • Ok, will try

                  • Will did not explain things very well.  The JOT server just stop responding and on the web side of things you get the connection ...... thing.  App.js is running and it is not related to a SSL cert expiring.  It has done this often.  Will contacts me, I check, the app is running, I terminate, restart and then it works until the next time it stops responding.  The app.js itself has a bug, Boonex is aware of this bug because it has been reported many times in the past.  I guess the solution is to create a cron job to stop and start JOT every two weeks for good measure or to just rip the bloody thing out and throw it away.  I am on the side of ripping the bloody thing out but it is Will's site so I will support it like a good sys admin.  However, Boonex needs to own up on the bug even if you don't want to fix it.

                    • I sit here reading this and imagined intestines, heart and everything else ripped out and hung in different locations with a Gothic touch. Blood covers the floor like a velvet blanket.. Such beauty macabre... awesome!

                      • Hello!

                        We are working on the new Jot Messenger versions and there are many new features and abilities are added also corrections for Jot Server.

                        Geek Girl, concerning certificate problem: we are working on this issue too. Server will be restarted if any of the files involved in the work of the server is changed. I have mentioned about it in couple of posts already. 

                        Login or Join to comment.