SSO Facebook - no icon @login page?

Solved Technical Support

Suggested Topics


  • 0 Votes
    11 Posts
    411 Views

    @RandomAnimeGamer what you mean it recommends specifying a port? Here's a quote from the guide:

    Note: When entering your site URL, make sure it is exactly what you plan on accessing your site at. If you plan on visiting http://example.org to open your forum, then enter exactly http://example.org.

  • 0 Votes
    1 Posts
    239 Views

    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

    or

    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": "127.0.0.1",
    "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 http://127.0.0.1:4567; 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!

  • 2 Votes
    20 Posts
    1k Views

    @julian I found this: https://github.com/NodeBB/NodeBB/issues/4734
    Using the certbot configuration, I edited /etc/nginx/sites-available/default

    Leaving the certbot managed parts as they are, my custom config looks like this now:

    proxy_set_header X-Forwarded-Proto $scheme; location / { proxy_pass http://127.0.0.1:4567; }

    The special part is the x-forwarded-proto line, that's what I was needing all along.

    And in /home/nodebb/nodebb/config.json I'm setting the URL with https:

    { "url": "https://forums.mydomain.com", "secret": "<REDACTED>", "database": "mongo", "port": "4567", "mongo": { "host": "127.0.0.1", "port": "27017", "username": "nodebb", "password": "<REDACTED>", "database": "nodebb", "uri": "" } }

    This resolved my problem.

  • 0 Votes
    2 Posts
    613 Views
    I do not believe the mobile header is configurable out of the box, just the left-hand menu. You can enable search for guests from ACP > Manage > Privileges (global)
  • 1 Votes
    8 Posts
    3k Views

    @sonia @baris we should launch shouldn't we... :trollface:

    After 0.7.0 I think we wanted to launch weekly or something