Status v1.1.0
-
I see that V1.1.0 is released. Safe to upgrade from v1.0.3 ? Feel free to post issues in this thread!
-
-
the image
I hope all my plugins work with v1.1.0 : Plugin list
I guess i will try to update tomorrow!
-
In other words
Add this in your nginx conf (Server block) (After X-Forwarded-For)
proxy_set_header X-Forwarded-Proto $scheme;
if you are using Nginx before NodeBB in all cases?
-
At the moment i have
location / { proxy_http_version 1.1; proxy_set_header Connection "upgrade"; proxy_pass http://forum-mammagrupper-com:4567; proxy_set_header Host $host; proxy_set_header Upgrade $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Real-IP $remote_addr; }
correct should be
location / { proxy_http_version 1.1; proxy_set_header Connection "upgrade"; proxy_pass http://forum-mammagrupper-com:4567; proxy_set_header Host $host; proxy_set_header Upgrade $http_upgrade; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; }
Right? Is it safe to always have proxy_set_header X-Forwarded-Proto $scheme; set?
If something else looks crappy, feel free to point it out -
This is an old bug
- Klick update
- Klick activate
- stop Nodebb and start Nodebb from the console.
If it now works, check the file perms (Nodebb user must have write access to everything). Later on you can restore your perms after updating and enable of emoj
My dev is updated now and no problems yet. Will continue to test ... I be Back !
-
We updated at MangoLassi and all seems well.
-
Works on all my 3 dev sites. Seams good !
-
You can view the list of closed issues on github for a detailed insight.
-
-