Skip to content
Sudonix

Gettin Erors NodeBB

Solved Configure
7 2 1.3k 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

    Difficult to move posts now, on mobile.

    Bugs nodebb
    16
    1
    5 Votes
    16 Posts
    4k Views
    phenomlabundefined
    @DownPW Yes, it is. It’s set far too low meaning other elements with a higher preference will sit over the top of it.
  • Pandaundefined

    Further Widgets question

    Solved Configure nodebb
    4
    1
    1 Votes
    4 Posts
    984 Views
    phenomlabundefined
    @Panda category is for a category in its own, so for example, “fruit” whereas categories is the page that contains all categories as a list.
  • cagatayundefined

    NodeBB v3 Chat Very Slow

    Moved Performance nodebb v3 nodebb chat
    47
    11 Votes
    47 Posts
    13k Views
    phenomlabundefined
    @DownPW Seems fine.
  • mventuresundefined

    NodeBB: Opening the Composer for replies

    Solved Configure cms composer
    2
    0 Votes
    2 Posts
    762 Views
    phenomlabundefined
    @mventures Quick reply is basically exactly that. However, it’s possible to trigger the full composer as below [image: 1681314389744-82ca1209-31be-4a51-a641-9887b5a238b8-image.png] Failing that, you’ll need to use the reply button in the sticky toolbar [image: 1681314442570-1d230bcb-ff8e-4756-94f7-6e2fb7a94bc4-image.png]
  • mventuresundefined

    NodeBB: Creating the Swatch modes

    Solved Configure swatch
    2
    0 Votes
    2 Posts
    679 Views
    phenomlabundefined
    @mventures the swatch feature you refer to isn’t a NodeBB plugin, but a utility that I wrote that handles this. It is available for v2 (as you can see here) but I’ve stopped developing and releasing the code because it has been entirely rewritten to work for v3. If you’d like the code, this is possible, but you’ll need to upgrade to v3 first.
  • DownPWundefined

    NODEBB: Nginx error performance & High CPU

    Solved Performance performance nodebb nginx
    69
    4
    14 Votes
    69 Posts
    36k Views
    DownPWundefined
    @phenomlab Seems to be better with some scaling fix for redis on redis.conf. I haven’t seen the message yet since the changes I made # I increase it to the value of /proc/sys/net/core/somaxconn tcp-backlog 4096 # I'm uncommenting because it can slow down Redis. Uncommented by default !!!!!!!!!!!!!!!!!!! #save 900 1 #save 300 10 #save 60 10000 If you have other Redis optimizations. I take all your advice https://severalnines.com/blog/performance-tuning-redis/
  • marusakyundefined

    Configure SMTP for Nodebb

    Solved Configure
    14
    5 Votes
    14 Posts
    3k Views
    phenomlabundefined
    @marusaky based on the work completed thus far (in relation to PM exchanges), I’m going to mark this completed. Sending email from the server itself works fine without issue, and DNS appears to be clean (valid SPF, DMARC, and DKIM records). It appears that only Gmail marks incoming messages from your domain as spam - perhaps because of the domain age, which there is nothing we can do to prevent this. Mail delivery to all other domains appears to work fine in al of my tests.
  • crazycellsundefined

    background color of the footer area

    Solved Customisation nodebb
    7
    1
    7 Votes
    7 Posts
    2k Views
    crazycellsundefined
    @phenomlab thank you very much