Community

Invalid csrf token and Failed login attemp

Technical Support

Suggested Topics

  • T

    Need to change login link to some other route

    Technical Support
    0 Votes
    7 Posts
    876 Views
    GnanaPrakash RathinamG

    I dont see a way to disable login under Settings -> User, using NodeBB version 1.12.2

  • I

    nodebb upgrade fails with Error: schema-out-of-date

    Technical Support
    0 Votes
    5 Posts
    1973 Views
    julianJ

    What does node app --upgrade net you?

  • danielflippanceD

    Login Page (Almost ) Blank - Can't Login

    Technical Support
    0 Votes
    1 Posts
    1082 Views
    danielflippanceD

    My login page is (almost) entirely blank on my production server but works ok on dev and staging (heroku). I can see the home page and I can create an account and see the profile page, but I cannot login to an existing account:

    0_1458589372352_Screen Shot 2016-03-21 at 12.41.34 PM.png

    There are no javascript errors in the browser and no errors in the server side log:

    21/3 14:33 [24540] - info: NodeBB v0.9.2 Copyright (C) 2013-2014 NodeBB Inc.
    21/3 14:33 [24540] - info: This program comes with ABSOLUTELY NO WARRANTY.
    21/3 14:33 [24540] - info: This is free software, and you are welcome to redistribute it under certain conditions.
    21/3 14:33 [24540] - info:
    21/3 14:33 [24540] - info: Time: Mon Mar 21 2016 14:33:07 GMT-0500 (PET)
    21/3 14:33 [24540] - info: Initializing NodeBB v0.9.2
    21/3 14:33 [24540] - info: Environment: production
    21/3 14:33 [24540] - verbose: * using mongo store at xx.xx.xx.xx:xxxx
    21/3 14:33 [24540] - verbose: * using themes stored in: /var/www/blahblahblah/live/node_modules
    21/3 14:33 [24540] - info: [database] Checking database indices.
    21/3 14:33 [24540] - verbose: Checking dependencies for outdated modules
    21/3 14:33 [24540] - verbose: [notifications.init] Registering jobs.
    21/3 14:33 [24540] - verbose: [meta/css] Minifying LESS/CSS
    21/3 14:33 [24540] - verbose: [sounds] Sounds OK
    21/3 14:33 [24540] - verbose: [meta/templates] Compiling templates
    21/3 14:33 [24540] - verbose: [meta/templates] Successfully compiled templates.
    21/3 14:33 [24540] - verbose: [meta/css] admin.css committed to disk.
    21/3 14:33 [24540] - verbose: [meta/css] stylesheet.css committed to disk.
    21/3 14:33 [24540] - verbose: [meta/js] Minification complete
    21/3 14:33 [24540] - verbose: [hotswap] Router with id plugins replaced successfully
    21/3 14:33 [24540] - verbose: [plugins] All plugins reloaded and rerouted
    21/3 14:33 [24540] - verbose: [hotswap] Router with id auth replaced successfully
    21/3 14:33 [24540] - verbose: [meta/js] Client-side minfile committed to disk.
    21/3 14:33 [24540] - info: NodeBB Ready
    21/3 14:33 [24540] - info: Enabling 'trust proxy'
    21/3 14:33 [24540] - info: NodeBB is now listening on: 0.0.0.0:4567

  • D

    invalid csrf token in NodeBB 0.7.x

    Technical Support
    0 Votes
    3 Posts
    1468 Views
    M

    I've found the issue. The problem was coming from the varnish's configuration, which was playing the set-cookie value.

  • Moritz FriedrichM

    CSRF error when logging in after URL change

    Technical Support
    0 Votes
    6 Posts
    3159 Views
    julianJ

    @Moritz-Friedrich said:

    Weird enough, I just realized that at the old subdomain (as a CNAME) logging in is still possible...

    Default this is not set to anything, so this doesn't need to be set... afaik

Copyright © 2023 NodeBB | Contributors