@pitaj Something similar to MyBB's template and CSS editor where I can edit the templates and css stylesheets within the admin panel.

Is their an exporter for NodeBB to switch back to MyBB or other forum software?

To elaborate more: NodeBB is good software but without a CSS and Template Editor it simply doesn't meet my needs and I'd like to switch back to MyBB if at all possible.

I would like to get into theme development for NodeBB (I don't have $3,000 to pay the core team to do things for me) however unless I'm insane there's not a html template nor CSS editor. What resources are out there to help me get into theme development on NodeBB?

@shard I probably have the world's most unique edgecase

Sidenote for huge IP Ban Lists run the following bash script:

for i in `cat ./list.txt`; do echo 'deny' $i';' >> denyips.conf; done

list.txt being a list of IP addresses/ranges one IP / Range per line, denyips.conf being the file you give to the nginx proxy.

root@vps146875:/etc/nginx# wc -l ./denyips.conf
158740 ./denyips.conf

it took like a second to do it's thing very fast for so many lines.

@julian Ok on staging I ran nodebb reset -p to deactivate all plugins, I ran th commands to upgrade, and now nodebb is running at 100% CPU on the staging server.

root@NodeBB-Staging:/var/www/html/NodeBB# curl -I http://127.0.0.1:4567
curl: (7) Failed to connect to 127.0.0.1 port 4567: Connection refused
root@NodeBB-Staging:/var/www/html/NodeBB# ./nodebb log

Hit Ctrl-C to exit

This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain conditions.
For the full license, please visit: http://www.gnu.org/copyleft/gpl.html

Clustering enabled: Spinning up 1 process(es).

16/10 15:17:25 [3728] - info: Initializing NodeBB v1.6.1 https://staging.sinfulforums.net:443
16/10 15:17:25 [3728] - warn: You have no mongo username/password setup!
16/10 15:17:28 [3728] - info: [socket.io] Restricting access to origin: *:*
16/10 15:17:28 [3728] - info: Routes added

CPU and RAM at 100% utilization by the way.

@julian Sorry about the delays, file transfers took a bit longer than expected. I have a staging server setup at https://staging.sinfulforums.net/login/2fa, if you'd like I can send you SSH Credentials to Staging. I'm fixing a few things regarding plugins. It still has certain plugins deactivated breaking login so I'm working on a fix for that then we can start working on an upgrade tactic.

@julian Staging server will be ready in 10 minutes. In SSH now I just need a few minutes to setup.

I was able to successfully rollback to 1.6.0 however I'd still like to upgrade to 1.6.1 as soon as possible. Now that I'm all rolled back, what steps do you recommend I take to upgrade?

After upgrading to NodeBB 1.6.1 I am unable to start the service.

./nodebb dev output:

root@vps146875:/var/www/sinfulforumsnet/NodeBB# ./nodebb dev

NodeBB v1.6.1 Copyright (C) 2013-2014 NodeBB Inc.
This program comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to redistribute it under certain conditions.
For the full license, please visit: http://www.gnu.org/copyleft/gpl.html

Clustering enabled: Spinning up 1 process(es).

16/10 09:22:46 [1783] - verbose: * using configuration stored in: /var/www/sinfulforumsnet/NodeBB/config.json
16/10 09:22:46 [1783] - info: Initializing NodeBB v1.6.1 https://sinfulforums.net:443
16/10 09:22:46 [1783] - verbose: * using mongo store at 127.0.0.1:27017
16/10 09:22:46 [1783] - verbose: * using themes stored in: /var/www/sinfulforumsnet/NodeBB/node_modules
16/10 09:22:46 [1783] - warn: You have no mongo username/password setup!
16/10 09:22:50 [1783] - verbose: [minifier] utilizing a maximum of 0 additional threads
16/10 09:22:50 [1783] - verbose: Checking dependencies for outdated modules
16/10 09:22:51 [1783] - verbose: [notifications.init] Registering jobs.
16/10 09:22:51 [1783] - verbose: [user/jobs] (Re-)starting user jobs...
16/10 09:22:51 [1783] - verbose: [user/jobs] Starting job (digest.daily)
16/10 09:22:51 [1783] - verbose: [user/jobs] Starting job (digest.weekly)
16/10 09:22:51 [1783] - verbose: [user/jobs] Starting job (digest.monthly)
16/10 09:22:51 [1783] - verbose: [user/jobs] Starting job (reset.clean)
16/10 09:22:51 [1783] - verbose: [user/jobs] 4 jobs started
16/10 09:22:51 [1783] - verbose: [emailer] Setting up SMTP fallback transport
16/10 09:22:51 [1783] - info: [themes] Using theme nodebb-theme-persona
16/10 09:22:51 [1783] - verbose: [plugins] Initializing plugins system
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-composer-default
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-theme-persona
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-markdown
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-mentions
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-widget-essentials
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-rewards-essentials
16/10 09:22:51 [1783] - verbose: [plugins] Found 3 sound file(s) for plugin nodebb-plugin-soundpack-default
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-soundpack-default
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-emoji-extended
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-emoji-one
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-2factor
16/10 09:22:51 [1783] - warn: [plugins/nodebb-plugin-spam-be-gone] Hook `action:flag.create` is deprecated, please use `action:flags.create` instead.
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-spam-be-gone
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-emailer-smtp
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-dbsearch
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-emailer-sendgrid
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-imgur
16/10 09:22:51 [1783] - verbose: [plugins] Loaded plugin: nodebb-plugin-desktop-notifications
16/10 09:22:51 [1783] - info: [plugins] Plugins OK
16/10 09:22:52 [1783] - info: [plugins/spam-be-gone] Settings loaded
16/10 09:22:52 [1783] - verbose: [hotswap] Router with id `plugins` replaced successfully
16/10 09:22:52 [1783] - verbose: [plugins] All plugins reloaded and rerouted
16/10 09:22:52 [1783] - verbose: [hotswap] Router with id `auth` replaced successfully
16/10 09:22:52 [1783] - info: Routes added

NodeBB reports as started however it won't listen to incoming connections. If I run ./nodebb stop the processes don't stop until I run killall node.

I've tried the following:

• A git hard reset to v.1.6.x
• ./nodebb reset -p to reset the plugins

My production site is currently down. What's the recommended action to get it back up and running?

Sidenote: NodeBB runs at 100% CPU and won't stop processes without a reboot.

@pitaj said in Add limits on global moderators:

Privileges refactor

Will do and thanks for linking

Is there a plugin that uses the stopforumspam api to block spam registrations. I know about spambegone but I want something that uses the stopforumspam api to block at registration time so I don't have to delete spam registrations later.

So I found a small but rather frustrating bug (don't judge by title) in NodeBB.

If you add an IP Ban - no user is able to register, including IP Addressses that are not supposed to be IP Banned, an error occurs well the full html of an error displays saying NodeBB is unable to match the IPs the error message is just an html blob, it doesn't display properly. Initially I thought this could be a cloudflare caused issue so I disabled things like minify, rocketloader, etc and cleared caches on cloudflare and my local system, however the problem persisted, the full html in error message likely wasn't a cloudflare caused issue otherwise other registration errors would also display as full html [Purposely failing the captcha https://i.imgur.com/5XooFnB.png the error displays fine]). However with Cloudflare enabled, NodeBB is unable to match IPs and therefore the IP Bans feature cannot be used. My workaround is to issue IP Bans at Cloudflare Level however it'd be nice if I could use the NodeBB Built in one. Thoughts?

Nginx Configuration:

user www-data;
worker_processes auto;
pid /run/nginx.pid;

events {
	worker_connections 2048;
	multi_accept on;
	use epoll;
}

http {

	##
	# Basic Settings
	##

	sendfile on;
	tcp_nopush on;
	tcp_nodelay on;
	keepalive_timeout 120;
	types_hash_max_size 2048;
	server_tokens off;

	##
	# Security Options
	##
	client_max_body_size 100m;

	# server_names_hash_bucket_size 64;
	# server_name_in_redirect off;

	include /etc/nginx/mime.types;
	default_type application/octet-stream;

	##
	# SSL Settings
	##

	ssl_protocols TLSv1 TLSv1.1 TLSv1.2; # Dropping SSLv3, ref: POODLE
	ssl_prefer_server_ciphers on;

	##
	# Logging Settings
	##

	access_log /var/log/nginx/access.log;
	error_log /var/log/nginx/error.log;

	##
	# Gzip Settings
	##

	gzip on;
	gzip_disable "msie6";

	gzip_vary on;
	gzip_proxied any;
	gzip_comp_level 6;
	gzip_buffers 16 8k;
	gzip_http_version 1.1;
	gzip_types text/plain text/css application/json application/javascript text/xml application/xml application/xml+rss text/javascript;

	##
	# Virtual Host Configs
	##
	include /etc/nginx/sites-enabled/*;
	include /etc/nginx/ipbans.conf;

##
# Cloudflare Set Real IP
##
set_real_ip_from 103.21.244.0/22;
set_real_ip_from 103.22.200.0/22;
set_real_ip_from 103.31.4.0/22;
set_real_ip_from 104.16.0.0/12;
set_real_ip_from 108.162.192.0/18;
set_real_ip_from 131.0.72.0/22;
set_real_ip_from 141.101.64.0/18;
set_real_ip_from 162.158.0.0/15;
set_real_ip_from 172.64.0.0/13;
set_real_ip_from 173.245.48.0/20;
set_real_ip_from 188.114.96.0/20;
set_real_ip_from 190.93.240.0/20;
set_real_ip_from 197.234.240.0/22;
set_real_ip_from 198.41.128.0/17;
set_real_ip_from 2400:cb00::/32;
set_real_ip_from 2606:4700::/32;
set_real_ip_from 2803:f800::/32;
set_real_ip_from 2405:b500::/32;
set_real_ip_from 2405:8100::/32;
set_real_ip_from 2c0f:f248::/32;
set_real_ip_from 2a06:98c0::/29;
real_ip_header CF-Connecting-IP;
}

server {
	listen 80;
	listen 443 ssl;
	root /var/www/html/;
	index index.html;
	server_name sinfulforums.net www.sinfulforums.net;


	# Main Location Block
	location / {
		proxy_http_version 1.1;
		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
		proxy_set_header X-Forwarded-Proto $scheme;
	        proxy_set_header X-Real-IP $remote_addr;
		proxy_set_header Upgrade $http_upgrade;
		proxy_set_header Connection 'upgrade';
		proxy_set_header Host $host;
		proxy_set_header X-NginX-Proxy true;
		proxy_redirect off;
		proxy_pass http://127.0.0.1:4567;

			types {
				application/javascript jst js;
				text/css css;
			}
	}


	# SSL Configuration
	ssl_certificate /etc/nginx/ssl/cert.pem;
	ssl_certificate_key /etc/nginx/ssl/privkey.pem;
	ssl_session_cache shared:SSL:10m;
	ssl_session_timeout 10m;
	ssl_protocols TLSv1.2;
	ssl_prefer_server_ciphers on;
	ssl_ciphers AES256+EECDH:AES256+EDH:!aNULL;
	ssl_client_certificate /etc/nginx/ssl/originpull.pem;
        ssl_verify_client on;
	ssl_dhparam ssl/dhparam.pem;
	ssl_ecdh_curve secp384r1;
}

Currently the only way to accomplish what I am asking is thru category level permissions however for global moderators I'd like to prevent them from purging users (double check this one - im not sure if global mods can delete users) / topics / posts and only allow them to soft delete them. Thoughts?

@dangeruss This is a minor issue however a solution would be nice.

So far so good

I have multiple categories and changing permissions for each one would take way too much time.

So I noticed that on the desktop theme I only have two search buttons in both mobile and desktop mode and am not sure if this is expected behavior. On desktop is appears one is quick search, though the same does not apply on mobile (maybe hide the second one on mobile). I double checked things by uninstalling and reinstalling the search plugin and it remained the same. Thoughts?

Is that all I need just to proxy through nginx, that's what I'm currently doing, I saw that plugin in settings and thought I was doing something wrong. I just wanted to confirm I'm doing everything properly.

I saw the api encrypt plugin was removed from github. Do you still need it for https to work properly or what this built into nodebb?