Connection lost when attempting to upload a new profile picture or cover picture

[PitaJ]

That is what is causing the issue I think. What os and node version are you using?

[mimo]

On Debian 9, a Digital Ocean droplet.

[baris]

What nodejs version? Last time I tried sharp didn't have binaries for node11, not sure if it has now.

[mimo]

We're using NodeJS version 11.3.0

If there isn't a compatible sharp module, is there an alternative we can use so that we can keep using the picture uploading?

[baris]

Can you switch to node 10.x until it is added?

[mimo]

We'll give that a shot.

[baris]

See https://github.com/lovell/sharp/issues/1464

[mimo]

Unfortunately, after downgrading NodeJS to 10.14.2 we still get the same error on the upload screen. As for using the upload by URL option, we get the "misconfigured CORS" error, which seems unrelated.

[baris]

Did you run npm install after downgrading node?

[mimo]

Yes, npm install was run afterwards

[mimo]

After more testing with both the direct upload and URL upload, I am even more confused. The direct upload is still not working but when I try the URL upload I get different error messages depending on the browser I use. Note the image I am uploading is coming from imgur.com using https and the latest versions of the respective browsers.

• Chrome: "Unable to upload image due to misconfigured CORS"

• Edge: "SecurityError"

• IE 11: "SecurityError"

• Firefox: "The operation is insecure."

• Opera: "Unable to upload image due to misconfigured CORS"

The inconsistencies are frustrating, any suggestions on what is causing this?

[Anjin]

I had this problem as well, also impacted image uploading in messages.

First updated to the newest nodebb release (1.11.0) and Node.js stable @ (11.2).

Tried to downgrade Node.js back to (10.12) with no love.

Returned to Node.js stable (11.2), and fixed by simply building sharp locally.

npm install --build-from-source sharp

Cheers
Anjin

[mimo]

@Anjin That worked! Holy cow it worked! Thank you for that.

[sharonyue]

I run into this problem as well, and I fixed it by simply npm install --build-from-source sharp, FYI.