I upgraded yesterday as soon as I saw the update posted.
so far so good.

Ive been running NodeBB for my support forum for a little over a year now, and are super happy with it:
support.sweetpproductions.com

I also included css support for dark mode in my custom theme.

@julian nice one!

I’ve a actually been running one of the later betas in production for a week or so with no issues.

Looking forward to the final release.

no problems on my forums as far as I can tell.
instant search is great, awesome work!

@scottalanmiller my support forum has pretty low traffic, so it’s not really an issue

Actually the version of postgresql I had to install on my server doesn’t seem to be compatible with my install of Plesk either.

But it works well, and I don’t have to mess around learning how to support mongodb.

I had the same issue, and fixed it by changing the Skin in my user settings

I managed to get the uploads working by adding the following to my Apache & nginx Settings on the Additional nginx directives in my Plesk Onyx panel:

location / {
	proxy_set_header X-Real-IP $remote_addr;
	proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
	proxy_set_header X-Forwarded-Proto $scheme;
	proxy_set_header Host $http_host;
	proxy_set_header X-NginX-Proxy true;

	proxy_pass http://127.0.0.1:4567;
	proxy_redirect off;

	# Socket.IO Support
	proxy_http_version 1.1;
	proxy_set_header Upgrade $http_upgrade;
	proxy_set_header Connection "upgrade";
}

thanks @PitaJ, Im ok with that, I'll probably never run the command again. In this particular case, I changed the structure of my forum and moved a large number of topics into different categories.

I finally got the error fixed.
here's what happened, I am running a Plesk Onyx server, and installed the NodeJS update according to this guide:

And while everything looked good within Plesk, when I ran the command:

node -v

the old v8.9.1 of NodeJS would show as being current...

so all I did was this:

nvm use 10.15
npm install
npm rebuild

now everything is finally running just fine again

@baris thanks,
there are so many configuration options, it takes time to find things
I found the option on Settings>User if anyone else is looking for it

@julian nice one!

I’ve a actually been running one of the later betas in production for a week or so with no issues.

Looking forward to the final release.

fixed with the following patch:
https://github.com/NodeBB/NodeBB/commit/6a5e86dc667a42009bcac0c7061a21b6717cf9a9

0 barisusakli committed to NodeBB/NodeBB

fix: #8305, don't use null values

I get an update error

4. Updating NodeBB data store schema...
Parsing upgrade scripts... 
OK | 1 script(s) found, 83 skipped
  → [2020/5/2] Fix user sorted sets...
    [######       ] (500/1021) 48% (node:14753) UnhandledPromiseRejectionWarning: error: null value in column "score" violates not-null constraint
    at Connection.parseE (/var/www/vhosts/website.com/NodeBB/node_modules/pg/lib/connection.js:581:48)
    at Connection.parseMessage (/var/www/vhosts/website.com/NodeBB/node_modules/pg/lib/connection.js:380:19)
    at Socket.<anonymous> (/var/www/vhosts/website.com/NodeBB/node_modules/pg/lib/connection.js:116:22)
    at Socket.emit (events.js:198:13)
    at addChunk (_stream_readable.js:288:12)
    at readableAddChunk (_stream_readable.js:269:11)
    at Socket.Readable.push (_stream_readable.js:224:10)
    at TCP.onStreamRead [as onread] (internal/stream_base_commons.js:94:17)
(node:14753) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:14753) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code

Ive been running NodeBB for my support forum for a little over a year now, and are super happy with it:
support.sweetpproductions.com

I also included css support for dark mode in my custom theme.

thanks @PitaJ, Im ok with that, I'll probably never run the command again. In this particular case, I changed the structure of my forum and moved a large number of topics into different categories.

So, after searching through the source code, and comparing topics - I ended up altering my Postgres database instead, with the following query:
UPDATE legacy_hash SET data = data - 'oldCid';

I havn't seen any adverse affects... is there something which I need to be aware of?

does someone have a solution to this?

no problems for my Ubuntu 18.04/Postgres update either

I had the same issue, and fixed it by changing the Skin in my user settings

I upgraded yesterday as soon as I saw the update posted.
so far so good.