@JaredBusch said:

A quick firewall-cmd --zone=public --add-port=4567/tcp --permanent and firewall-cmd --reload later
And there we go.

Thanks @rbeer for the information about nodejs versions. I did not see the indicator that you did obviously.

Very nice! Glad to see it working now.
And, don't you worry! I was tearing my hair out for about an hour, when I stumbled upon that error some weeks ago.

@xen
Binding a port through your ssh connection is actually quite simple.
(The following assumes that you are using the OpenSSH client on GNU/Linux)

tl;dr:
https://youtu.be/vC7Smc67gPg

1. Start the SSH client with ssh user@remotehost.com -L 7000:localhost:6379
   So basically like you would normally do, appending -L ... with the syntax:
   • local_port:interface_on_remote:remote_port (ssh manpage)
2. You should have an interactive session to your remote, prompt and all or whatever your setup resolves into when logging in over SSH. Again, business as usual is expected here.
3. Now comes the good part: Since you tunneled your local port 7000 to the remotes localhost interface on (redis-) port 6379, you can create a new connection in Redis Desktop Manager, ignoring the SSH tab in the "New Connection" dialog and simply connecting to localhost:7000.

That might be true. I am not familiar with CentOS and its package management.

Replacing the install instructions in question with nodesource (https://github.com/nodesource/distributions/tree/master/), might be a good idea. I know e.g. that Debian also has 0.10.x in its repos.

All your logs and screenshots show a nodejs version 0.10.x. That's heavily outdated. Which manifests itself fataly in

../node_modules/nan/nan.h:328:47: error: ‘REPLACE_INVALID_UTF8’ is not a member of ‘v8::String’
   static const unsigned kReplaceInvalidUtf8 = v8::String::REPLACE_INVALID_UTF8;

i.e. a module, that needs compilation, can't find a member (REPLACE_INVALID_UTF8) of the String class in v8. It must have been introduced later. Upgrading to 0.12.x at least should solve this problem.

@rbeer said:

I'm curious about the contents of two files:

• /var/log/redis/redis-server.log
• /path/to/nodebb/log/nodebb.log

@wellenreiter

Hi @Pilvinen

I hope you didn't purge redis, already. That could have deleted the log file, as well.

I'm curious about the contents of two files:

• /var/log/redis/redis-server.log
• /path/to/nodebb/log/nodebb.log

Like all the others, I suspect redis itself to be the source of failure here. NodeBB uses the DB's flush (wipe all data) only in its tests; even there on a test-databse you'd have to set up explicitly.