@yariplus Nope, I just moved away from DO. And yes, for me also it was probably the 3rd time where I had to install a database package manually as previous attempts to apt-get install had failed or installed an outdated version. I really wish they updated database packages more often on Ubuntu repos, since my problem occurred only due to an outdated redis package on Ubuntu 16.04 (Xenial) repo.

I managed to fix the problem by uninstalling the redis-server service that I had installed via apt-get & manually installing the latest redis stable build which has an updated config to allow supervisors like systemd to supervise the process.

To anyone who's encountering the same issues, here's a decent tutorial on how to get Redis up and running on Ubuntu 16.04.

Ok, managed to get it working with systemd, however I ran into another issue. Redis starts, but kinda hangs and eventually the starting process timeouts. Any ideas?

As I look through the syslog, it seems that the starting process timeouts every ~2 minutes and then it tries to restart the server again. And it basically loops like that forever...
The forum itself is kinda working, but having some outages due to redis constantly restarting itself.

vps291166 systemd[1]: redis-server.service: Start operation timed out. Terminating.

Hey,

I'm currently migrating my NodeBB installation to another VPS and I came across an error when installing redis-server. The installation of redis-server went flawlessly, until I tried to check the status of Redis. (service redis-server status). It printed out a miscellaneous error with no information about what could be wrong... I've tried to fix this error for hours and I still can't figure out what could be the issue.
My first idea was that perhaps Ubuntu systemd was doing something nasty, because when manually starting Redis via $ redis-server, it started properly with no errors.

Error log when doing service redis-server status:

● redis-server.service - Advanced key-value store
   Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
   Active: inactive (dead) (Result: exit-code) since Sun 2016-06-26 15:11:08 CEST; 29min ago
     Docs: http://redis.io/documentation,
           man:redis-server(1)
  Process: 8492 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=1/FAILURE)
  Process: 8487 ExecStartPre=/bin/run-parts --verbose /etc/redis/redis-server.pre-up.d (code=exited, status=0/SUCCESS)

Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Control process exited, code=exited status=1
Jun 26 15:11:08 vps291166 systemd[1]: Failed to start Advanced key-value store.
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Unit entered failed state.
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Failed with result 'exit-code'.
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Service hold-off time over, scheduling restart.
Jun 26 15:11:08 vps291166 systemd[1]: Stopped Advanced key-value store.
Jun 26 15:11:08 vps291166 systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 26 15:11:08 vps291166 systemd[1]: Failed to start Advanced key-value store.

And service redis-server start just prints this line:

Job for redis-server.service failed because the control process exited with error code. See "systemctl status redis-server.service" and "journalctl -xe" for details.

Does anyone know how many "concurrent connections" they actually allow in Free plan?

If you want to use custom fonts, you should upload the font files (.woff etc.) into public folder and still declare them in Custom CSS.
However, I can't give you any examples as I've never tried it myself.
Perhaps this SO post can help...
http://stackoverflow.com/questions/12812441/how-do-i-use-woff-fonts-for-my-website

Perhaps this post can help?
https://community.nodebb.org/topic/4645/websocket-domain/4

According to the docs, it is not recommended to jump from 0.7.x to 0.9.x. Best practice at the moment would be to upgrade to the last version of 0.7.x branch, then proceed to 0.8.x and from there move on to 0.9.x.

More info here: https://docs.nodebb.org/en/latest/upgrading/index.html#upgrade-path

Well... If you already have NodeBB running on port 80 without nginx/Apache proxy, then you can not assign another service on the port as well. I recommend you to set up an nginx/Apache proxy for NodeBB and create virutal hosts for each service you want to run on port 80 (this way you can run multiple services/sites on port 80).

I suppose fresh Ubuntu 14.10 install will do the trick, if you don't mind losing data...

Is Redis server itself (as a service) running?
Check what Redis' status reports...

$ sudo service redis-server status

@julian said:

In addition, we now have a nodebb-plugin-gravatar, so this one sounds like an improvement on the old one even though they're completely different

If only it had the same features, as Gravatar Extended has .

@JLChnToZ
Hi, it seems that the plugin doesn't work on v0.9.x branch.

I would try reinstalling MongoDB if possible...

Updated to master & works like a charm ;).

@zack said:

updated to nginx 1.8. and problem persist
notice this is not a cloudfare problem, browsing directly with server ip will end with same error if you put more than 1 port on node config , even with 1 port i´m getting 1 error 400 each minute.
if you click on one of them you get this
{"code":1,"message":"Session ID unknown"}

I have exactly the same situation.

Edit: I changed config.json a little bit.

"socket.io": {
    "transports" : ["websocket"]
}

This seems to solve the polling errors in console (quite obvious lol), but the "lost connection to forum" still keeps appearing on the navbar every minute or so.

@KingCat

Sadly, your solution does not work in my case .
It's kinda weird indeed - works flawlessly on Chrome, spams errors on Safari.
I'm really starting to think it's Safari's bug...

@pitaj said:

How is the plugin so far? Have you encountered any bugs?

BTW, @markkus, there are translatable strings. Look here

I haven't tried it yet. I'll give it a shot once you've released the npm package.

And thanks for the heads up, I'll probably produce Estonian translation once I get my hands on it.

@KingCat said:

Welp, I solved it.

Turns out I had the wrong directory specified in nginx for static assets.

Could you tell me exactly step-by-step what you did? Seems like the error has come back...

Hi,

It would be really cool if the future releases of NodeBB would feature an option to give infractions to other members who have broken the rules. (this option would be available to forum moderators). It would be also great if certain groups would have the ability to ban/unban members (also forum moderators).

I also think that the category permissions section should be moved under the groups & users management section in ACP. At the moment, it is really tedious to set permissions for each group in multiple categories (Each time I'd have to navigate inside the category and fill in the checkboxes for every category when a new group is created.).

Tbh, it's hard to explain, but I hope you get the idea.