Make sure you have a backup/snapshot to revert to, in case of any issues

another alternative to try (arch based distro) is manjaro.

try removing the port (:4567)

@fish I'd also like to know... maybe I can correct it, or elaborate a bit more about it.

as the documentation is pretty good, so far.

which version of mongodb are you using?

@frgilb I'm not using cloudflare though (mentioned in the other thread you posted).

I haven't gotten around to doing this fix yet... but I will try it, when I have the time. work, work, work

I have the same issue.

I will give this a shot and see if this works.

@lupin-kang said in NodeBB 1.6.0: faster (rendering) and prettier (emails):

hello world!

Hello human...

the ultimate questions are...

what instance are you running? 1 vcore 1GB VM? bigger? smaller?

Do you have swap? in case you don't have enough memory...

is the DB on the same server as nginx and nodebb? separate?

Which OS are you running?

If these questions were answered, please point me to it, and I will see if I can help

interesting... usually I just restart the service (systemctl restart nodebb, if you haven't created it as a service, one can run ./nodebb stop && ./nodebb start, or you can just go with ./nodebb restart, I prefer stopping and starting it... old windows habits)... then I run ./nodebb build and after that refresh my browser (ctrl + F5).

See if that works

try running ./nodebb build

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

make sure you have port 80 and/or 443 open on your firewall. I see 80 is open (I get the "Welcome to Nginx" message). So now you need to make a few changes in your nginx config for it to redirect 4567 to your site on 80/443 (http/https), as currently it is set to the nginx page.

The docs has a config you can use, just make the changes like Pitaj has suggested and for https, you will need a certificate. Lets-Encrypt is free

**Edit to add: Don't forget to restart nginx to use the new config

as a last ditch effort... I did it again, but upgrading with the nodebb account...

v1.4 ---> v1.5 = perfect

v1.5 ---> v1.6 = now I don't get internal server error, but pages get stuck ~75% and when I manually refresh, it works (*edit to add: for every page I go to, besides login and admin).

I'm sticking to v1.5 until I can find the time and strength to reinstall it to v1.6

@pitaj that part I already know. I am a sysadmin as well... freebsd habits, when it comes to starting services (I am not really in the mood to explain admin tasks for spinning up services in any OS with an admin/root account, too tired for that now).

short answer could've been:

due to changes to v1.6.0, it is mandatory to use the account that you use for nodebb for upgrading, to avoid extra admin work and/or issues.

off to bed with me ;(

@pitaj aaah ok... so what step should I change to update it properly then? let my nodebb account run ./nodebb upgrade or should I let my account fetch/checkout/merge as well (which I will have to modify some policies for that)?

@pitaj but it doesn't explain why when I do this from v1.4 to 1.5 it works fine, but v1.5 to v1.6 it doesn't work. If that was one of the changes in the upgrade parameter, then I will try it with my nodebb account (which my service file is using nodebb.service)

@julian is that one of the changes?

the 2 lines I ran was literally this (as root):
systemctl stop nodebb; git fetch; git checkout v1.5.x; git merge origin/v1.5.x; ./nodebb upgrade; systemctl start nodebb

wait a minute and the forum works, without an issue (upgrading from v1.4.6 to v1.5.3)

next (as root):
systemctl stop nodebb; git fetch; git checkout v1.6.x; git merge origin/v1.6.x; ./nodebb upgrade; systemctl start nodebb
File ownership is not correct (might be due to extra files not being there, due to older release) and once ownership is corrected, pages get stuck until it is refreshed.

Should I try a different branch, maybe?

@pitaj but why with this particular version? from v1.4.x to v1.5.x was perfectly fine... now I should be doing it with my nodebb account? That should be added to the docs, I think. My nodebb account is literally just a service account [nologin account with selinux limiting it too, and correct policies are applied to it too]...

yes, is that a problem? with previous version, I did the same thing and worked perfectly