Occurred when hitting /users/. Content loaded but profile image hung for awhile:29/5 14:32  - info: NodeBB Ready 29/5 14:32  - info: Enabling 'trust proxy' 29/5 14:32  - info: NodeBB is now listening on: 0.0.0.0:4568 29/5 14:32  - info: [plugins/spam-be-gone] Settings loaded 29/5 14:32  - info: NodeBB Ready 29/5 14:32  - info: Enabling 'trust proxy' 29/5 14:32  - info: NodeBB is now listening on: 0.0.0.0:4567 29/5 15:40  - error: /trackback/ invalid csrf token
@Guiri First stop is
@julian Yes. Turns out I had to
echo 1 > /proc/sys/vm/overcommit_memory. The forum has been running great!
Hey @julian, I've just installed NodeBB again on a clean Droplet, following psychobunnys noob guide for reference, and when logging in I got the same error. The page stops at
/?loggedinwith 500 Internal Server Error, api/config/ also has the same error, removing `/?loggedin' takes me back to the homepage, and I am logged in though.
I went into NodeBBs logs and saw this
node_redis: no callback to send error: ERR unknown command 'pexpire'
/var/log/redis, the only error in there was about
overcommit_memoryneeding to be set to 1.
Have I set up a duff droplet on Digital Ocean or something? I've installed NodeBB about 3 or 4 times now, but never had this issue.
What version is your redis? You can see in the ACP>database. Looks like pexpire is only supported on redis 2.6.0 and up.
@baris Seems that could be the issue then, as it states my Redis version is 2.2.12.
Have updated to version 2.8.9. Must have missed a command somewhere.
Seems it hasn't been fixed.
I get this running
Oh and redis version is 2.8.4, not 2.8.9. Ubuntu version is 14.04 if this helps.
Oh and everything worked fine until I tried enabling some plugins, installed and enabled, clicked Home to restart nodebb, page didn't change, so tried loading homepage, nada, have reset all plugins, still getting the issue.
Edit: a quick git pull (1 deletion) & ./nodebb upgrade later and it seems to be ok, one of the plugins seems to be the cause. Trying to figure out which one.
Culprit seems to be plugin-emoji-extended, although I've no idea why. Enabling that plugin gives me the csrf error, disabling makes the error go away.
the first error seems to be my fault: #1517 sorry for that
It appears within emoji-extended now because I recently updated to the new settings framework
But I have no clue what the
TypeError: Cannot read property '_csrf' of undefinedis about... maybe it disappears when the first one is fixed.
Just merged the above fix, let me know if your error is fixed after pulling latest
@psychobunny That's done the trick, no csrf error when enabling emoji-extended.