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.
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.
@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:
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:
@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:
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
@PitaJ still no luck
Im running on Centos 7 if that makes any difference
I recently upgraded from nodejs 9.10.1 to 10.15.0, and the problem has come back
ERROR
Something went wrong while parsing server response
[Error] Failed to load resource: the server responded with a status of 502 () (upload, line 0)
https://support.sweetpproductions.com/api/post/upload
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";
}
im still getting 502 errors when trying to upload:
[Error] Failed to load resource: the server responded with a status of 502 () (upload, line 0)
https://support.sweetpproductions.com/api/post/upload
I fixed the deletion of orphaned files by changing file permissions on my NOdeBB install, but I still can't upload new images.
Im having trouble with image uploads, and always get this:
ERROR
Something went wrong while parsing server response
I also get this error when trying to delete orphaned images from the Manage/Uploads
admin page:
ΓERROR
EACCES: permission denied, unlink '/var/www/vhosts/.../NodeBB/public/uploads/files/1540629625930-4c7e9f63-94d1-4d0f-a73b-9b77513956e1-image.png'
maybe its a permissions issue
the public folder in my install is owned by root, is that correct?