Definitely seems like cache issue with the record for express-session. try sudo npm cache clean? After that try manually clearing the cache files?

@fr3em1nd said: @a_5mith yep fuser -k 3000/tcp seem to fix it so it will kill all to processes using that port It may do work. But it is not very clean and can lead to serious problems to solve problems of this kind that way. Just a little advice. No offence.

i have use the Arch linux, Arch linux is great, but after startup, is not start eth0 this is really bad, i can't connect with ssh, and i must restart the network via the web. maybe is this problem ? i try new on ubuntu Nodebb with redis.. but why to install a nginx ?