@wayne-workman that is actually a very good idea that we can also use... We do sometimes give people 1 week or 2 weeks "temporary" bans, which would look better if not tagged as "banned", so it is more obvious for all the users... it would be good to have options such as "inactive" , "frozen" , "penalized" etc.

@baris said in Badges not showing: You can turn on multiple badges at /admin/settings/group oh nice, didn't even think about that as we've had badges for so long Just turned it on for us, too.

@wayne-workman I said to run npm install, not ./nodebb install

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

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.

Nevermind, figured it out. Inside of config.json there is the url field and a port field... I had a port inside of the URL field, and I removed the port from the url and restarted nodebb, and it's working now!

I figured it out, soon as I put the FQDN into config.json, the FQDN address started working and the local IP stopped. Good enough for me.