NodeBB connection has been lost, attempting to reconnect

Hi,
I paid somebody to install nodebb for me and all was going fine, i had a subdomain setup on my site so it would point to my vps with nodebb installed on it. Everything was fine until I tried to post another post and It told me that connection had been lost. I've tried restarting it multiple times and it still won't work.

Suggested Topics

In nodebb's case it will just need the A (or E... which will be nginx. Don't ask me why the E stands for nginx, as that is how they named the stack. Maybe because it is pronounced engine-x) and the M... for mongodb

You would need to edit the theme, to change the widget areas and sizes. The current widget system isn't advanced enough to do that alone. Also, the widgets currently reload every page change, which will look strange if widget content doesn't. But overall, it would work.
I would ditch the widgets and use a theme with that as the main layout. Then if you need to change the side bar, you can use some simple js to change it when a particular page is loading. Of course, this would not work if you are planning to use a lot of the existing widgets.

@meetdilip said:
@a_5mith
A few doubts,
Copy files from folder to which we have installed ?
The github repo, so you'd have a folder called nodebb with all of the nodebb files in, then a folder called nodebb2, which also contains all the nodebb files.
Share the command to change port no. please..
./nodebb setup, but change :4567 to something else.
How to assign new folder / installation to database 2 ?
You answered this in your next post, change the 0 in database to 1.
Should we run ./nodebb setup after copying the files ( installed ? ) to a new folder ?
You will need to yes in order to set it up, you'll also need to run npm install to get the dependencies installed in that location.

Solved!
Soo, there appeared to be two errors. One with the nginx config which I solved in the past ( a / typo behind the proxy_pass ) for anyone having this same issue make sure you double check the nginx rules for a typo.
Secondly a npm rebuild fixed all the issues.
Thanks for the help guys!