Login to Widget

Technical Support

Suggested Topics

  • How to disable local login at setup?

    Unsolved Technical Support
    0 Votes
    4 Posts

    @julian I assumed that since this was a managed container environment where containers are ephemeral and can be moved around, I would need to run ./nodebb setup every time. Is my assumption wrong? Can I just run setup once to populate the database and then just run ./nodebb build the other times?

  • Undefined Page at Login

    Unsolved Technical Support
    0 Votes
    2 Posts

    Well, as you were. As if by magic, the issue resolved. Nevermind!

  • 0 Votes
    1 Posts

    like title, how can i modify widget on "/recent" router? how can add ex: recent post, recent view... widget on this screen?

  • 0 Votes
    1 Posts

    I am running a nodebb 1.15.0 system on Ubuntu 20 on nginx. It's a newer install and we've had an occasional issue on both registration and login where folks will get a message denying their login or registration.

    2020-11-12T06:11:19.312Z [4567/17870] - error: /register
    invalid csrf token


    2020-11-12T06:11:13.910Z [4567/17870] - error: /login
    invalid csrf token

    Frequently a refresh on the browser will let a user login or sometimes just waiting a few minutes.

    Here's my config.json

    "url": "https://opposite-lock.com",
    "secret": "secret",
    "database": "mongo",
    "port": "4567",
    "mongo": {
    "host": "",
    "port": "27017",
    "username": "nodebb",
    "password": "secret",
    "database": "nodebb",
    "uri": ""


    Nginx config

    server {

    server_name opposite-lock.com; client_max_body_size 100M; location / { proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $http_host; proxy_set_header X-NginX-Proxy true; proxy_pass; proxy_redirect off; # Socket.IO Support proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } listen 443 ssl; # managed by Certbot ssl_certificate /etc/letsencrypt/live/opposite-lock.com/fullchain.pem; # managed by Certbot ssl_certificate_key /etc/letsencrypt/live/opposite-lock.com/privkey.pem; # managed by Certbot include /etc/letsencrypt/options-ssl-nginx.conf; # managed by Certbot ssl_dhparam /etc/letsencrypt/ssl-dhparams.pem; # managed by Certbot

    server {
    if ($host = opposite-lock.com) {
    return 301 https://$host$request_uri;
    } # managed by Certbot

    listen 80; server_name opposite-lock.com; return 404; # managed by Certbot


    Any help would be very much appreciated!

  • 1 Votes
    4 Posts

    @FrankM said in Probmes with login after upgrading to 1.11.0:

    But in config.json i have http://...... Edit it to https:// solved the problem.
    Before version 1.11.0 i don't have this problem.

    Thanks, that solved the problem for me as well, changing http to https. And as for you, I did not have this problem before 1.11.0

    But then an other problem turned up: "Invalid CSRF Token"

    Pls see this link https://community.nodebb.org/topic/9222/invalid-csrf-token

    My solution for this was what is written in the end (I use Apache2)

    for the record for people finding this via search, for apache2 you have to set this somewhere in your nodebb vhost configuration
    with ssl

    RequestHeader set X-Forwarded-Proto "https"

    without ssl

    RequestHeader set X-Forwarded-Proto "http"

    you might have to enable mod_headers to do so!

    So upgrading to 1.11.0 gave me a problem that had to be solved in 2 steps. First by changing in config.json, then I had to modify Apache2 settings.