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

@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

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

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";
}

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:

Install additional node versions in Plesk Onyx

This a guidance not a problem to solve, to help those which have the same issue I had Enable Node support in Plesk Onyx: Install the "Node support" simply from your "update and updates" Plesk int...

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

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.

@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

is it possible to receive email notifications when new posts are queued for review?
I was recently caught out by this with a number of posts stuck in limbo

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

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:

Install additional node versions in Plesk Onyx

This a guidance not a problem to solve, to help those which have the same issue I had Enable Node support in Plesk Onyx: Install the "Node support" simply from your "update and updates" Plesk int...

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

ah, I didn't post, because it's virtually identical to the previous output:

npm rebuild --build-from-source

npm rebuild --build-from-source · GitHub

@PitaJ said in image upload issues:

npm rebuild --build-from-source

still get the error, unfortunately

ERROR
Something went wrong while parsing server response

here's the full output:

NodeBB v1.1.2 npm rebuild

NodeBB v1.1.2 npm rebuild · GitHub

I then also chown the NodeBB directory, then:

systemctl stop nodebb
systemctl start nodebb

I have also update to NodeBB v1.1.2 and still have the same issue