Hi,

I'm experiencing this issue with nodeBB where after a successful login, the URL has double http addresses in it, which gives the user an error. The user can then click on "categories" and be taken to categories no problem. But the initial landing page is problematic.

Suppose my domain name is forums.mydomain.com
After a successful login, I'm taken to this URL:
https://forums.mydomain.com/https://forums.mydomain.com

I'm running NodeBB version 1.11.2

What settings would I change to fix this?

Thanks,
Wayne

I did get this working.
I moved the nodebb working directory to /home/nodebb/nodebb and changed ownership of that to nodebb:nodebb, now it starts up on boot as the nodebb user just fine.

Thank you all very much for the help.

Hello,

One of my group's members passed away recently. I'd like to secure his NodeBB forums account, but the only way I see to do it is by banning him. He's not banned, he's just gone. I don't want that ugly red "BANNED" flag by his name, it is disrespectful.

What other options are there to secure a user's account? Can I choose what banner they get? Can I choose to not display the "Banned" flag anywhere?

I would suggest allowing custom banners for disabled accounts, individually:

• Banned
• Inactive
• No label shown anywhere.

Thanks,
Wayne

Hi,

I have a perfectly healthy installation of nodeBB at home on Debian9, works great if I start it with ./nodebb start but I'm trying to get systemd to start it.

I've found this: https://docs.nodebb.org/configuring/running/ which was a big step in the right direction.

My nodebb directory is here: /root/nodebb
and I've made a user called nodebb

This .service file works:

[Unit]
Description=NodeBB
Documentation=https://docs.nodebb.org
After=system.slice multi-user.target mongod.service

[Service]
Type=forking
User=root

StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=nodebb

WorkingDirectory=/root/nodebb
ExecStart=/usr/bin/env node loader.js
Restart=always

[Install]
WantedBy=multi-user.target

When I change the user from root to nodebb, and do a systemctl daemon-reload (or a reboot), and then try to start the service, it fails. These are the errors that appear in the system journal:

-- Unit nodebb.service has begun starting up.
Feb 25 18:55:34 debian nodebb[854]: internal/modules/cjs/loader.js:583
Feb 25 18:55:34 debian nodebb[854]:     throw err;
Feb 25 18:55:34 debian nodebb[854]:     ^
Feb 25 18:55:34 debian nodebb[854]: Error: Cannot find module '/root/nodebb/loader.js'
Feb 25 18:55:34 debian nodebb[854]:     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15)
Feb 25 18:55:34 debian nodebb[854]:     at Function.Module._load (internal/modules/cjs/loader.js:507:25)
Feb 25 18:55:34 debian nodebb[854]:     at Function.Module.runMain (internal/modules/cjs/loader.js:742:12)
Feb 25 18:55:34 debian nodebb[854]:     at startup (internal/bootstrap/node.js:283:19)
Feb 25 18:55:34 debian nodebb[854]:     at bootstrapNodeJSCore (internal/bootstrap/node.js:743:3)
Feb 25 18:55:34 debian systemd[1]: nodebb.service: Control process exited, code=exited status=1
Feb 25 18:55:34 debian systemd[1]: Failed to start NodeBB.
-- Subject: Unit nodebb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nodebb.service has failed.
-- 
-- The result is failed.
Feb 25 18:55:34 debian systemd[1]: nodebb.service: Unit entered failed state.
Feb 25 18:55:34 debian systemd[1]: nodebb.service: Failed with result 'exit-code'.
Feb 25 18:55:35 debian systemd[1]: nodebb.service: Service hold-off time over, scheduling restart.
Feb 25 18:55:35 debian systemd[1]: Stopped NodeBB.
-- Subject: Unit nodebb.service has finished shutting down
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nodebb.service has finished shutting down.
Feb 25 18:55:35 debian systemd[1]: nodebb.service: Start request repeated too quickly.
Feb 25 18:55:35 debian systemd[1]: Failed to start NodeBB.
-- Subject: Unit nodebb.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
-- 
-- Unit nodebb.service has failed.

I've ensured that the nodebb user owns the /root/nodebb directory with
chown -R nodebb:nodebb /root/nodebb

Any ideas?

@FrankM Thanks for your help. I did that, still not working.

Hi NodeBB people, you folks are awesome. I have a minor, not critical problem that I am asking for help with. I've made a new group called 'Officers'. There's two users in that group. One of those users's badge shows in the forums, the other users badge doesn't show.

I did do some google searching for "nodebb badge not showing" and I found some pretty old posts, like 2+ years old. So I thought I'd open a new thread. Hope that's alright.

Details:
NodeBB version: v1.12.0
Node version: v10.15.3
OS: Debian 9

Details that may or may not matter:
The user who's badge shows is not a member of administrators, the user who's badge does not show is also a member of administrators.

Steps I've taken:
Removed users and re-added them. Rebuilt & restarted forums. Refreshed browser. Deleted & recreated the group. No happiness from any of those.

For the user whose badge doesn't show - no badge shows for him at all. I've got the forums setup so that administrator badges are not shown. But I do want to display officer badges.

Please help? What to do? I have no idea.

Thanks,
Wayne

@PitaJ This solved it for me. Thank you.

@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.