@atozsoft There was really no need to reinstall NodeBB... within 24 hours the account would have automatically unlocked 😄
SOLVED Upgrade to 1.16.2 - "reply" broken in Chrome after browser reload
After upgrading to 1.16.2 the "reply" functionality no longer works if the page is reloaded
To create the issue:
- Start with fresh login
- Test reply works (it does)
- Normal reload of the browser (CTRL-R)
- Test reply - does not work, button does nothing
Errors in Chrome console immediately after logging in:
Errors in Chrome console immediately after sending CTRL-R:
Basically identical errors but now reply is not working. clicking the button/link for reply does not generate more errors, the clicks are ignored.
There is one error in the nodebb logs which may be related:
Error: Session Mismatch at validateSession (/home/nodebb/nodebb_root/src/socket.io/index.js:196:9) at runMicrotasks (<anonymous>) at processTicksAndRejections (internal/process/task_queues.js:97:5) at async onMessage (/home/nodebb/nodebb_root/src/socket.io/index.js:143:3)
Nothing obvious in the nginx access or error logs
Redis version 4.0.9
Node v12.21.0 (Tried with node v14 as in the documentation but that had other errors that were fixed with a downgrade)
This is with the latest version of Chrome
Running with clustering enabling so the big change in this upgrade was having to install redis to allow that to work. As redis is now handling the sessions could that be the reason this is not working?
As an possibly related issue, I am used to using our forum from multiple browser sessions almost concurrently (e.g. on mobile, on desktop). I now see session mismatch errors occasionally when switching. For the purposes of this test above I only had one session open to keep it simple.
As a further update. this means that when a link to a forum post is pasted into a browser where you already have a logged in session the new tab is effectively a browser reload and thus reply does not work.
I note that with this version of chrome
the same errorssimilar errors are show with this forum:
however reply does work here, even after a CTRL-R reload
So I clearly have a misconfiguration somewhere in the backend.
Further update - Problem appears to be fixed.
One difference in browser errors is the prepareFooter error:
Uncaught ReferenceError: highlight is not defined at HTMLDocument.prepareFooter ((index):3508)
The java script was there to add functionality to highlight.js for syntax highlighting. now to dig into what has changed with highlight.js in the latest version.