Skip to content

Gettin Erors NodeBB

Solved Configure
7 2 1.8k 1
  • 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)
    
  • @cagatay interesting. Aside from the error messages, does this impact the forum operation itself?

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

  • 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)
    

    @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.

  • @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.

    @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.
    
  • @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.
    

    @cagatay which site was this taken from ?

  • @cagatay which site was this taken from ?

    @phenomlab efelsefe.

    uzayyolu is working without problem.

  • @phenomlab efelsefe.

    uzayyolu is working without problem.

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

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

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

  • phenomlabundefined phenomlab has marked this topic as solved on

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
  • What plugins are being used here on Sudonix?

    Solved General nodebb plugins development
    6
    5 Votes
    6 Posts
    2k Views
    @Roki-Antic Welcome! This site isn’t running Persona, but Harmony - a very heavily customised version at that. Do you have a URL where your site is currently located that is publicly accessible? Feel free to PM this info if you do not want to disclose here. Happy to help with any customisation needs.
  • CSS codes to prevent votes to disappear

    Solved Customisation nodebb
    3
    1 Votes
    3 Posts
    1k Views
    @phenomlab yes, it is thanks a lot…
  • Custom html in nodebb to prevent cache

    Unsolved Configure nodebb
    18
    2 Votes
    18 Posts
    4k Views
    @Panda You’ll need to do that with js. With some quick CSS changes, it looks like this [image: 1690796279348-d619844f-fbfe-4cf1-a283-6b7364f6bf18-image.png] The colour choice is still really hard on the eye, but at least you can now read the text
  • Composer options on nodebb

    Solved Configure nodebb
    8
    1
    3 Votes
    8 Posts
    2k Views
    @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; }
  • NodeBB upgrade now cant post

    Solved Bugs nodebb
    5
    2 Votes
    5 Posts
    2k Views
    @Panda yes, for some reason, that is the case. If you need an urgent response, it’s probably better to post here because of the time difference.
  • NodeBB: Upgrading to NodeBB v3.x

    Solved Configure nodebb v3.x
    6
    0 Votes
    6 Posts
    2k Views
    @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.
  • 36 Votes
    55 Posts
    22k Views
    @DownPW I see why. The code relies on the existence of [component="topic/quickreply/container"] However, this by definition means that the below has to be enabled [image: 1679077966615-aeef638f-4188-489d-a9f2-f3a26dbca9d8-image.png] It will then work [image: 1679077992245-7fb38631-e0f3-46ef-b652-00929d927b13-image.png] For some unknown reason, this is hidden in Harmony, and only shows if you select it. In v2, it seems that the <section> is deleted altogether in Persona if “Quick Reply” is disabled, meaning it won’t fire as it can’t locate that specific component. The downside is that you might not want the quick reply function, but I think it’s a PITA to scroll up to the top of the post just to reply, so I have it on
  • Iframely (Nodebb)

    Solved Configure
    40
    4 Votes
    40 Posts
    12k Views
    @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.