Skip to content
Sudonix

Gettin Erors NodeBB

Solved Configure
7 2 1.5k 1
  • cagatayundefined

    Hi,
    Started to get eror message as below;

    Error: revalidate-failure
    at validateSession (/home/nodes/nodebb/src/socket.io/index.js:216:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async onMessage (/home/nodes/nodebb/src/socket.io/index.js:153:3)
    0
  • phenomlabundefined phenomlab

    @cagatay interesting. Aside from the error messages, does this impact the forum operation itself?

    cagatayundefined

    @phenomlab no forum is working goods.
    there is no eror message since yestarday.

    0
  • cagatayundefined cagatay

    Hi,
    Started to get eror message as below;

    Error: revalidate-failure
    at validateSession (/home/nodes/nodebb/src/socket.io/index.js:216:9)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
    at async onMessage (/home/nodes/nodebb/src/socket.io/index.js:153:3)
    phenomlabundefined

    @cagatay That appears to be an issue with the socket service on your server. Does this happen frequently, and if so, how often ? For the most part, this is typically intermittent, but if it is occuring frequently, it does need to be checked.

    Mark – Founder, Phenomlab Ltd
    Executive IT & Security Leadership
    Phenomlab Ltd

    0
  • phenomlabundefined phenomlab

    @cagatay That appears to be an issue with the socket service on your server. Does this happen frequently, and if so, how often ? For the most part, this is typically intermittent, but if it is occuring frequently, it does need to be checked.

    cagatayundefined

    @phenomlab not often but now i see another eror;

    Error: Login sessions require session support. Did you forget to use `express-session` middleware?
    at SessionStrategy.authenticate (/home/nodes/nodebb/node_modules/passport/lib/strategies/session.js:46:41)
    at attempt (/home/nodes/nodebb/node_modules/passport/lib/middleware/authenticate.js:369:16)
    at authenticate (/home/nodes/nodebb/node_modules/passport/lib/middleware/authenticate.js:370:7)
    at Layer.handle [as handle_request] (/home/nodes/nodebb/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/nodes/nodebb/node_modules/express/lib/router/index.js:328:13)
    at /home/nodes/nodebb/node_modules/express/lib/router/index.js:286:9
    at Function.process_params (/home/nodes/nodebb/node_modules/express/lib/router/index.js:346:12)
    at next (/home/nodes/nodebb/node_modules/express/lib/router/index.js:280:10)
    at initialize (/home/nodes/nodebb/node_modules/passport/lib/middleware/initialize.js:98:5)
    at Layer.handle [as handle_request] (/home/nodes/nodebb/node_modules/express/lib/router/layer.js:95:5)
2022-11-08T17:00:00.020Z [4567/223452] - info: [user/jobs] Did not send digests (day) because subscription system is disabled.
    0
  • cagatayundefined cagatay

    @phenomlab not often but now i see another eror;

    Error: Login sessions require session support. Did you forget to use `express-session` middleware?
    at SessionStrategy.authenticate (/home/nodes/nodebb/node_modules/passport/lib/strategies/session.js:46:41)
    at attempt (/home/nodes/nodebb/node_modules/passport/lib/middleware/authenticate.js:369:16)
    at authenticate (/home/nodes/nodebb/node_modules/passport/lib/middleware/authenticate.js:370:7)
    at Layer.handle [as handle_request] (/home/nodes/nodebb/node_modules/express/lib/router/layer.js:95:5)
    at trim_prefix (/home/nodes/nodebb/node_modules/express/lib/router/index.js:328:13)
    at /home/nodes/nodebb/node_modules/express/lib/router/index.js:286:9
    at Function.process_params (/home/nodes/nodebb/node_modules/express/lib/router/index.js:346:12)
    at next (/home/nodes/nodebb/node_modules/express/lib/router/index.js:280:10)
    at initialize (/home/nodes/nodebb/node_modules/passport/lib/middleware/initialize.js:98:5)
    at Layer.handle [as handle_request] (/home/nodes/nodebb/node_modules/express/lib/router/layer.js:95:5)
2022-11-08T17:00:00.020Z [4567/223452] - info: [user/jobs] Did not send digests (day) because subscription system is disabled.
    phenomlabundefined

    @cagatay which site was this taken from ?

    Mark – Founder, Phenomlab Ltd
    Executive IT & Security Leadership
    Phenomlab Ltd

    0
  • phenomlabundefined phenomlab

    @cagatay which site was this taken from ?

    cagatayundefined

    @phenomlab efelsefe.

    uzayyolu is working without problem.

    0
  • cagatayundefined cagatay

    @phenomlab efelsefe.

    uzayyolu is working without problem.

    phenomlabundefined

    @cagatay interesting. Aside from the error messages, does this impact the forum operation itself?

    Mark – Founder, Phenomlab Ltd
    Executive IT & Security Leadership
    Phenomlab Ltd

    0
  • phenomlabundefined phenomlab

    @cagatay interesting. Aside from the error messages, does this impact the forum operation itself?

    cagatayundefined

    @phenomlab no forum is working goods.
    there is no eror message since yestarday.

    0
  • phenomlabundefined phenomlab has marked this topic as solved on
Log in to reply

Did this solution help you?
Did you find the suggested solution useful? Support 💗 Sudonix with a coffee ☕
If your organisation needs deeper expertise around infrastructure, security, or technology leadership, learn more about Phenomlab Ltd. Many of the deeper technical guides behind Sudonix are published there.

Related Topics
  • Pandaundefined

    Opening links in nodebb widget

    Solved Configure nodebb
    6
    4 Votes
    6 Posts
    2k Views
    phenomlabundefined
    A more efficient way of including this would be to not over complicate it and leverage a standard iframe (providing the CSP headers of the remote site permit this) like below <iframe src="https://www.classmarker.com/online-test/start/?quiz=gag66aea7922f0a5" width="700" height="800"></iframe> This works first time every time on your site as intended.
  • Pandaundefined

    Composer options on nodebb

    Solved Configure nodebb
    8
    1
    3 Votes
    8 Posts
    2k Views
    phenomlabundefined
    @Panda You should be able to expose the CSS for these using F12 to get into console [image: 1686833368846-3591518c-e3a3-4ada-a43c-6b32a5e0359c-image.png] [image: 1686833399483-a2b8ed46-4157-4ff2-85f0-576543380107-image.png] That should then expose the element once selected [image: 1686833431032-89d9c545-a47a-40d1-98f4-80cf3b958e8f-image.png] Here’s the below CSS you need based on the screenshot provided. .composer .formatting-bar .formatting-group li[data-format="picture-o"], .composer .formatting-bar .formatting-group li[data-format="spoiler"] { display: none; }
  • mventuresundefined

    NodeBB: Consent page

    Solved Configure nodebb consent
    16
    4 Votes
    16 Posts
    4k Views
    phenomlabundefined
    @DownPW I still do not see any issues.
  • mventuresundefined

    NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    2k Views
    phenomlabundefined
    @mventures You’d need to connect to the server and execute it directly - not on your local terminal. Review the guide below, which will show you how to gain access via SSH to your server https://docs.ovh.com/gb/en/dedicated/ssh-introduction/ Once you have access, you’ll need to navigate to the actual folder where NodeBB is installed You’ll then need to change to the directory as shown below /home/unbuntu/nodebb [image: 1680448167972-fdffe673-bf63-4b6d-a728-5506fddc1aff-image.png] In most cases, initial access takes you to the root of the file system. You can always issue pwd in a Linux terminal which will show you the Present Working Directory. From there, you can issue the command cd /home/ubuntu/nodebb Once in the NodeBB directory, you’d use the below commands ./nodebb stop git fetch && git checkout develop && git reset --hard origin/develop ./nodebb upgrade ./nodebb start Line 1 stops the NodeBB instance Line 2 gets the latest files from GIT (repository) and then checks out the development branch. It then resets the version you are using to the development branch ready for v3 Line 3 Runs the upgrade once the new branch is set, and code pulled Line 4 Restarts the NodeBB instance after the upgrade has completed Note that when you restart NodeBB and log back in, things will look very different to what you had in v2.
  • mventuresundefined

    NodeBB: Creating pages

    Solved Configure nodebb create page
    9
    0 Votes
    9 Posts
    3k Views
    mventuresundefined
    OK, I think I have figured out how to place a link in the footer which will click to a new page.
  • cagatayundefined

    Q&A Plugin Changes NodeBB

    Solved Customisation nodebb q&a plugin
    25
    1
    6 Votes
    25 Posts
    7k Views
    cagatayundefined
    @phenomlab said in Q&A Plugin Changes NodeBB: float: right; left: 10px; } worked thank you
  • crazycellsundefined

    creating topic specific widgets

    Solved Customisation nodebb
    16
    10 Votes
    16 Posts
    4k Views
    phenomlabundefined
    @crazycells said in creating topic specific widgets: Additionally if hide class exists, why are we re-defining it? We’re not 🤭 I misspelled it - it should be hidden
  • JACundefined

    Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    10k Views
    phenomlabundefined
    @DownPW This is now resolved. The issue was an incorrect URL specified in the Nodebb plugin. I’ve corrected this, and now it works as intended.