@yariplus I'm on stable.

@boomzilla Thanks for the info. I'm on CentOS and not using docker. I'll take a look at that sometime soon. It's late thought and it's been a long day.

@LukeLaupheimer That's beautifully terrible. Once it crashes again and I (maybe) get some useful info.. I'll do something like that.

I don't ruby. Is that a loop? Or do I need to set a cron to run it every x minutes? Also.. my http is a 301 to https. Will that work with https also?

Assuming I was starting a project where I am allocating portions of the profit to entities that offer us free things such as forum software to house community chit chat... who/where would I donate to in order to support NodeBB?

Looks like moving to the latest node.js did not help. Just happened again.

Bad news is that I crashed with absolutely no errors a few minutes ago. The good news is that it actually recovered on it's on in dev mode. I'll try updating nodejs as recommended.

@LukeLaupheimer That's beautifully terrible. Once it crashes again and I (maybe) get some useful info.. I'll do something like that.

I don't ruby. Is that a loop? Or do I need to set a cron to run it every x minutes? Also.. my http is a 301 to https. Will that work with https also?

@yariplus I'm on stable.

@boomzilla Thanks for the info. I'm on CentOS and not using docker. I'll take a look at that sometime soon. It's late thought and it's been a long day.

@pichalite That'd work if I didn't just scp it to another server.

@yariplus Good question. I'm honestly not sure. I just followed the install directions. I think I'm on the stable. :3 Is there an easy way to tell? My logs just say "Initializing NodeBB v1.0.3".

• What's your servers hardware?
  Core i3-2130/3240 3.4 GHz+ | 8 GB Ram
• What operating system runs on your server?
  CentOS 7.2
• What's your Redis Mongo version?
  mongodb 3.2.7
• What's your NGINX version?
  nginx 1.6.3
• What's your NGINX config?

server {
    listen         80;
    server_name     domain.com www.domain.com;
    return         301 https://www.domain.com/$request_uri;
}
server {
    ssl_certificate /etc/letsencrypt/live/www.domain.com/fullchain.pem;
    ssl_certificate_key /etc/letsencrypt/live/www.domain.com/privkey.pem;

    listen 443 ssl;

    add_header Strict-Transport-Security "max-age=31536000";
    server_name www.domain.com;

    location / {
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $http_host;
        proxy_set_header X-NginX-Proxy true;

        proxy_pass http://127.0.0.1:4567/;
        proxy_ssl_session_reuse off;
        proxy_redirect off;

        # Socket.IO Support
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
    }
}

• What else is running on the server which might interfere with NodeBB / Redis (especially IO extensive tasks like backups)?
  Confluence. The server doesn't even hiccup right now though. Not much traffic.
• Is your server using swap at all / a lot of swap during the times of lag?
  Negative. It's not lag. The server just stops.. but the daemon stays up. The only fix is to kill the service and start it up again
• Have you tried running NodeBB in verbose mode?
  Not recently. Running in dev and logging to a file now. I'll provide relevant stuff the next time it crashes.

You aren't alone here. I've been dealing with the same thing. It weird because the supervisor service still sees it as online, but nginx returns a 502. I have yet to find a good way to deal with this. It seems to have started on 1.0.3, so I've been considering going back down to 1.0.2.

Ahh. Gotcha. Thanks for that. I'll submit an issue.