Community

How to install NodeBB with Redis?

Moved Technical Support

Suggested Topics

  • F

    Why new accounts created by api doesn't work with nodebb-plugin-session-sharing

    Solved Technical Support
    2 Votes
    1 Posts
    145 Views

    F

    Hello,
    I created some accounts with the api/v3, but those accounts can't log in by email on the forum, and consequently can't log in with session sharing plugin.

    I searched a long time, because this used to work on nodebb v1.15.
    But on v1.18, some db objects are only set after the call of confirmByUid function :

    ['email:uid', uid, currentEmail.toLowerCase()], ['email:sorted', 0, `${currentEmail.toLowerCase()}:${uid}`], [`user:${uid}:emails`, Date.now(), `${currentEmail}:${Date.now()}`]

    So you have to confirm each account before the plugin "session sharing" works with them.

    To resolve this, i made a custom plugin and used the "confirmByUid" function :

    library.js :

    const Users = require.main.require('./src/user') var Plugin = { onCreateUser: function (postData) { const { user } = postData; Users.email.confirmByUid(user.uid); Topics.markAllRead(user.uid); } }

    plugin.json :

    "library": "./library.js", "hooks": [ { "hook": "action:user.create", "method": "onCreateUser" }, ]

    I hope this can help ;).

  • setkyarS

    Looks like your connection to NodeBB was lost, please wait while we try to reconnect.

    Technical Support
    0 Votes
    4 Posts
    2335 Views

    julianJ

    The common causes for a session mismatch error are usually one of the following:

    1. Mis-configured URL parameter in your config.json file

    If you have a misconfigured url value in your config.json file, the cookie may be saved incorrectly (or not at all), causing a session mismatch error. Please ensure that the link you are accessing your site with and the url defined match.

    2. Improper/malformed cookieDomain set in ACP

    Sometimes admins set this value without realising that they probably don't need to set it at all. The default is perfectly fine. This is what the config looks like:

    Cookie Domain setting

    If this is set, you'll want to revert the setting by editing your database directly:

    Redis: hdel config cookieDomain
    MongoDB: db.objects.update({ _key: "config" }, { $set: "cookieDomain": "" });

    3. Missing X-Forwarded-Proto header from nginx/apache

    If you are using a reverse proxy, you will need to have nginx pass a header through to NodeBB so it correctly determines the correct cookie secure property.

    In nginx, you will need to add the directive like so:

    location / { ... proxy_set_header X-Forwarded-Proto $scheme; ... }
  • C

    Upgraded NodeBB To V1.4.2 Errors

    Technical Support
    0 Votes
    3 Posts
    1221 Views

    C

    @pichalite Thank you for the response.

    That was most peculiar, but I reset the config.json to be how it was and it stopped having this error.

    Besides I still think it's best to check data.config, before extracting data.config.loggedin anyway.

  • R

    How do I make NodeBB run on port 80? (Noob)

    Technical Support
    0 Votes
    4 Posts
    2584 Views

    julianJ

    For Azure, perhaps this helps?

    Otherwise, our standard point of reference: https://docs.nodebb.org/en/latest/configuring/proxies.html

  • AtonB117A

    Using Cucina in a New Install; how to update?

    Moved Technical Support
    0 Votes
    1 Posts
    1068 Views

    AtonB117A

    Hey, yall.

    I'm wandering what is the process to update some of the older themes to work in 0.9.1. like the nice one below? Can I just follow the make a theme guide to use it to update an existing theme?

    Just trying to figure out what the work load would look like...

    Re: [nodebb-theme-cucina] Cucina Theme

| | | |
Copyright © 2023 NodeBB | Contributors