Any ideas? I tried installing older version of socket.io (1.4.8 instead of 1.7.1), made no difference.

I have dockerized existing Nodebb installation, transfered db to docker container too. Threads are shown correctly but I can't login at all - nodebb.example.com/login returns "Forbidden".

In front of nodebb there is reverse proxy. I get following errors when trying to login:

/ # npm -v
4.4.4
/ # node --version
v7.9.0

Log

app_1      | NodeBB v1.1.2 Copyright (C) 2013-2014 NodeBB Inc.
app_1      | This program comes with ABSOLUTELY NO WARRANTY.
app_1      | This is free software, and you are welcome to redistribute it under certain conditions.
app_1      | For the full license, please visit: http://www.gnu.org/copyleft/gpl.html
app_1      | 
app_1      | Clustering enabled: Spinning up 1 process(es).
app_1      | 
app_1      | 4/5 06:57 [21] - verbose: * using configuration stored in: /opt/nodebb/NodeBB-1.1.2/config.json
app_1      | 4/5 06:57 [21] - info: Time: Thu May 04 2017 06:57:39 GMT+0000 (UTC)
app_1      | 4/5 06:57 [21] - info: Initializing NodeBB v1.1.2
app_1      | 4/5 06:57 [21] - verbose: * using mongo store at mongodb:27017
app_1      | 4/5 06:57 [21] - verbose: * using themes stored in: /opt/nodebb/NodeBB-1.1.2/node_modules
app_1      | 4/5 06:57 [21] - info: [database] Checking database indices.
app_1      | 4/5 06:57 [21] - verbose: Checking dependencies for outdated modules
app_1      | 4/5 06:57 [21] - verbose: [notifications.init] Registering jobs.
app_1      | 4/5 06:57 [21] - info: [themes] Using theme nodebb-theme-persona
app_1      | 4/5 06:57 [21] - verbose: [plugins] Initializing plugins system
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 5 js file(s) for plugin nodebb-theme-persona
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-theme-persona/lib/persona.js
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-theme-persona/lib/modules/nprogress.js
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-theme-persona/lib/modules/autohidingnavbar.min.js
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-theme-persona/lib/modules/slideout.min.js
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-theme-persona/lib/client/chats.js
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 ACP js file(s) for plugin nodebb-theme-persona
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-theme-persona/lib/admin.js
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-theme-persona
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 less file(s) for plugin nodebb-plugin-composer-default
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 2 js file(s) for plugin nodebb-plugin-composer-default
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-plugin-composer-default/static/lib/client.js
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File not found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-plugin-composer-default/node_modules/screenfull/dist/screenfull.js (Ascending)
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/screenfull/dist/screenfull.js
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 ACP js file(s) for plugin nodebb-plugin-composer-default
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-plugin-composer-default/static/lib/admin.js
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 10 AMD-style module(s) for plugin nodebb-plugin-composer-default
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-plugin-composer-default
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 less file(s) for plugin nodebb-plugin-markdown
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 js file(s) for plugin nodebb-plugin-markdown
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-plugin-markdown/public/js/client.js
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 ACP js file(s) for plugin nodebb-plugin-markdown
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-plugin-markdown/public/js/admin.js
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 AMD-style module(s) for plugin nodebb-plugin-markdown
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-plugin-markdown
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 less file(s) for plugin nodebb-plugin-mentions
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 js file(s) for plugin nodebb-plugin-mentions
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-plugin-mentions/static/autofill.js
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-plugin-mentions
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 css file(s) for plugin nodebb-widget-essentials
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-widget-essentials
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 js file(s) for plugin nodebb-rewards-essentials
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-rewards-essentials/static/lib/main.js
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-rewards-essentials
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-plugin-soundpack-default
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 less file(s) for plugin nodebb-plugin-emoji-extended
app_1      | 4/5 06:57 [21] - verbose: [plugins] Found 1 js file(s) for plugin nodebb-plugin-emoji-extended
app_1      | 4/5 06:57 [21] - verbose: [plugins/load] File found: /opt/nodebb/NodeBB-1.1.2/node_modules/nodebb-plugin-emoji-extended/public/scripts/
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-plugin-emoji-extended
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-plugin-emoji-one
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loaded plugin: nodebb-plugin-dbsearch
app_1      | 4/5 06:57 [21] - info: [plugins] Plugins OK
app_1      | 4/5 06:57 [21] - verbose: [meta/js] 14 of 14 modules bridged
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loading templates (nodebb-theme-persona)
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loading templates (nodebb-plugin-composer-default)
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loading templates (nodebb-plugin-markdown)
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loading templates (nodebb-widget-essentials)
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loading templates (nodebb-plugin-emoji-extended)
app_1      | 4/5 06:57 [21] - verbose: [plugins] Loading templates (nodebb-plugin-dbsearch)
app_1      | 4/5 06:57 [21] - verbose: [meta/templates] Compiling templates
app_1      | 4/5 06:57 [21] - verbose: [meta/templates] Successfully compiled templates.
app_1      | 4/5 06:57 [21] - verbose: [meta/js] Minifying nodebb.min.js
app_1      | [minifier] file not found, node_modules/socket.io-client/socket.io.js
app_1      | 4/5 06:57 [21] - verbose: [meta/js] nodebb.min.js minification complete
app_1      | 4/5 06:57 [21] - verbose: [meta/js] Minifying acp.min.js
app_1      | [minifier] file not found, node_modules/socket.io-client/socket.io.js
app_1      | 4/5 06:57 [21] - verbose: [meta/js] acp.min.js minification complete
app_1      | 4/5 06:57 [21] - verbose: [meta/css] Minifying LESS/CSS
app_1      | 4/5 06:57 [21] - verbose: [meta/css] stylesheet.css committed to disk.
app_1      | 4/5 06:57 [21] - verbose: [meta/css] admin.css committed to disk.
app_1      | 4/5 06:57 [21] - info: NodeBB Ready
app_1      | 4/5 06:57 [21] - info: Enabling 'trust proxy'
app_1      | 4/5 06:57 [21] - info: NodeBB is now listening on: 0.0.0.0:4567
app_1      | 4/5 06:57 [21] - verbose: [sounds] Sounds OK
app_1      | 4/5 06:57 [21] - verbose: [meta/blacklist] Loading 0 blacklist rules
app_1      | 4/5 06:57 [21] - verbose: [hotswap] Router with id `plugins` replaced successfully
app_1      | 4/5 06:57 [21] - verbose: [plugins] All plugins reloaded and rerouted
app_1      | 4/5 06:57 [21] - verbose: [hotswap] Router with id `auth` replaced successfully
app_1      | 4/5 06:58 [21] - warn: Route requested but not found: /customHP
app_1      | 4/5 06:58 [21] - warn: Route requested but not found: /customHP
app_1      | 4/5 06:58 [21] - error: /login
app_1      |  invalid csrf token

config.json

{
    "url": "https://nodebb.example.com",
    "secret": "xxxxxxxxxxxxxx",
    "database": "mongo",
    "port": 4567,
    "mongo": {
        "host": "mongodb",
        "port": "27017",
        "username": "xxxxx",
        "password": "xxxxx",
        "database": "nodebb"
    },
    "socket.io": {
        "transports": ["websocket", "polling"],
        "address": "nodebb.example.com"
    }
}

Dockerfile

FROM mhart/alpine-node:4
ENV NODEBB_VERSION 1.1.2

RUN mkdir -p /opt/nodebb \
 && addgroup nodebb \
 && adduser -S -G nodebb -h /opt/nodebb -D nodebb \
 && chown -R nodebb:nodebb /opt/nodebb
RUN apk --update add curl

USER nodebb

RUN cd /opt/nodebb \
 && curl -L https://github.com/NodeBB/NodeBB/archive/v${NODEBB_VERSION}.tar.gz -o v${NODEBB_VERSION}.tar.gz \
 && tar xzf v${NODEBB_VERSION}.tar.gz 
 
RUN cd /opt/nodebb/NodeBB-${NODEBB_VERSION} && npm install --production

VOLUME ["/opt/nodebb/NodeBB-${NODEBB_VERSION}/public/uploads"]
CMD ["/bin/sh", "-c", "cd /opt/nodebb/NodeBB-${NODEBB_VERSION} && node app"]
EXPOSE 4567

Containers are setup with docker-compose, separate container for nodebb and database. Nodebb container is started with command: ["/bin/sh", "-c", "cd /opt/nodebb/NodeBB-1.1.2/ && ./nodebb dev"]

nginx conf

# If we receive X-Forwarded-Proto, pass it through; otherwise, pass along the
# scheme used to connect to this server
map $http_x_forwarded_proto $proxy_x_forwarded_proto {
  default $http_x_forwarded_proto;
  ''      $scheme;
}
# If we receive X-Forwarded-Port, pass it through; otherwise, pass along the
# server port the client connected to
map $http_x_forwarded_port $proxy_x_forwarded_port {
  default $http_x_forwarded_port;
  ''      $server_port;
}
# If we receive Upgrade, set Connection to "upgrade"; otherwise, delete any
# Connection header that may have been passed to this server
map $http_upgrade $proxy_connection {
  default upgrade;
  '' close;
}
# Set appropriate X-Forwarded-Ssl header
map $scheme $proxy_x_forwarded_ssl {
  default off;
  https on;
}
gzip_types text/plain text/css application/javascript application/json application/x-javascript text/xml application/xml application/xml+rss text/javascript;
log_format vhost '$host $remote_addr - $remote_user [$time_local] '
                 '"$request" $status $body_bytes_sent '
                 '"$http_referer" "$http_user_agent"';
access_log off;
# HTTP 1.1 support
proxy_http_version 1.1;
proxy_buffering off;
proxy_set_header Host $http_host;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $proxy_connection;
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 $proxy_x_forwarded_proto;
proxy_set_header X-Forwarded-Ssl $proxy_x_forwarded_ssl;
proxy_set_header X-Forwarded-Port $proxy_x_forwarded_port;
# Mitigate httpoxy attack (see README for details)
proxy_set_header Proxy "";
server {
    server_name _; # This is just an invalid value which will never trigger on a real hostname.
    listen 80;
    access_log /var/log/nginx/access.log vhost;
    return 503;
}

# nodebb.example.com
upstream nodebb.example.com {
        ## Can be connect with "back" network
      # nodebb_app_1
      #docker container IP
      server 172.21.0.2:4567;
}
server {
  server_name nodebb.example.com.com;
  listen 80 ;
  access_log /var/log/nginx/access.log vhost;
  return 301 https://$host$request_uri;
}
server {
  server_name nodebb.example.com;
  listen 443 ssl http2 ;
  access_log /var/log/nginx/access.log vhost;
  ssl_protocols TLSv1 TLSv1.1 TLSv1.2;
  ssl_ciphers 'ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-RSA-AES256-GCM-SHA384:DHE-RSA-AE
S128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA256:ECDHE-RSA-AES128-SHA256:ECDHE-ECDSA-AES128-SHA:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA384:ECDHE-ECDSA-AES256-
SHA:ECDHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA256:DHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES256-SHA:ECDHE-ECDSA-DES-CBC3-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES128-GCM-SHA256:AES256-GCM-
SHA384:AES128-SHA256:AES256-SHA256:AES128-SHA:AES256-SHA:DES-CBC3-SHA:!DSS';
  ssl_prefer_server_ciphers on;
    ssl_session_timeout 5m;
    ssl_session_cache shared:SSL:50m;
    ssl_session_tickets off;
    ssl_certificate /etc/nginx/certs/nodebb.example.com.crt;
    ssl_certificate_key /etc/nginx/certs/nodebb.example.com.key;
    ssl_dhparam /etc/nginx/certs/nodebb.example.com.dhparam.pem;
    add_header Strict-Transport-Security "max-age=31536000";
    include /etc/nginx/vhost.d/default;
    location / {
      proxy_pass http://nodebb.example.com;
    }
  }

I ran into similar problem some while ago and I used tags as a temporary solution. YMMV.

Not that I know of. Aren't they self-describing?
Could you explain where exactly are you stuck?

Transifex has CLI client - so you don't need to manually download all translation files.
https://docs.transifex.com/client/introduction

I must've missed 'Default user settings' part. Thanks!

I am aware of system group named registered-users which includes everyone, but I want to have "special" separated group of users beside registered-users.

I also noticed that when user is logged in one can see emails of all users on their profile page. Is it possible to turn this feature off? Or have I overlooked it in settings?

Seems like similar error which I've been experiencing lately (although I'm not using CentOs): https://community.nodebb.org/topic/9886/invalid-csrf-token/3

Perhaps we can figure it out together. Have you tried using older version like 1.1.2?

@julian Error seems to be occuring mostly to users using Safari (both mobile and desktop - MacOS). I don't have access to server right now, but will post additional data ASAP.

I'm getting 'invalid CSRF token' error and users sometimes can't login. Using version v1.1.2, nginx set as reverse proxy with SSL, header X-Forwarded-Proto set as recommended, cookieDomain is empty, plugins:

nodebb-plugin-canned-responses
nodebb-plugin-composer-default
nodebb-plugin-custom-homepg
nodebb-plugin-custom-pages
nodebb-plugin-markdown
nodebb-plugin-mentions
nodebb-plugin-merge-subtopics
nodebb-plugin-solr
nodebb-plugin-soundpack-default
nodebb-plugin-sso-facebook
nodebb-plugin-sso-google
nodebb-plugin-sso-twitter
nodebb-plugin-write-api
nodebb-rewards-essentials
nodebb-theme-persona
nodebb-widget-essentials

Log

 Error: Request aborted
    at onaborted (/opt/nodebb/NodeBB-1.1.2/node_modules/express/lib/response.js:973:15)
    at Immediate._onImmediate (/opt/nodebb/NodeBB-1.1.2/node_modules/express/lib/response.js:1015:9)
    at processImmediate [as _immediateCallback] (timers.js:383:17)
17/11 11:22 [170] - error: /login
 invalid csrf token
17/11 11:25 [170] - error: /login
 invalid csrf token
17/11 11:26 [170] - error: /login
 invalid csrf token
17/11 11:26 [170] - error: /login
 invalid csrf token
17/11 11:28 [170] - error: /login
 invalid csrf token
17/11 11:29 [170] - error: /login
 invalid csrf token
17/11 11:29 [170] - error: /login
 invalid csrf token
17/11 11:32 [170] - error: /login
 invalid csrf token
17/11 11:34 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:35 [170] - error: /login
 invalid csrf token
17/11 11:36 [170] - error: /login
 invalid csrf token
17/11 11:36 [170] - error: /login
 invalid csrf token
17/11 11:36 [170] - error: /login
 invalid csrf token
17/11 11:37 [170] - error: /login
 invalid csrf token
17/11 11:37 [170] - error: /login
 invalid csrf token
17/11 11:37 [170] - error: /login
 invalid csrf token
17/11 11:37 [170] - error: /login
 invalid csrf token
17/11 11:37 [170] - error: /login
 invalid csrf token
17/11 11:37 [170] - error: /login
 invalid csrf token
17/11 11:37 [170] - error: /login
 invalid csrf token
17/11 11:37 [170] - error: /login
 invalid csrf token
17/11 11:50 [170] - error: /login
 invalid csrf token
17/11 11:51 [170] - error: /login
 invalid csrf token
17/11 13:53 [170] - error: /login
 invalid csrf token
17/11 17:00 [170] - info: [user/jobs] Digest (day) scheduling completed.
17/11 18:36 [170] - warn: Flooding detected! Calls : 101, Duration : 5627
17/11 18:36 [170] - warn: [socket.io] Too many emits! Disconnecting uid : 0. Events : topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet
17/11 22:05 [170] - warn: Flooding detected! Calls : 101, Duration : 6061
17/11 22:05 [170] - warn: [socket.io] Too many emits! Disconnecting uid : 0. Events : topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet
17/11 22:45 [170] - error: /login
 invalid csrf token
18/11 12:31 [170] - error: /login
 invalid csrf token
18/11 17:00 [170] - info: [user/jobs] Digest (day) scheduling completed.
19/11 10:29 [170] - error: /plugins/nodebb-plugin-markdown/styles/railscasts.css
 Error: Request aborted
    at onaborted (/opt/nodebb/NodeBB-1.1.2/node_modules/express/lib/response.js:973:15)
    at Immediate._onImmediate (/opt/nodebb/NodeBB-1.1.2/node_modules/express/lib/response.js:1015:9)
    at processImmediate [as _immediateCallback] (timers.js:383:17)
19/11 17:00 [170] - info: [user/jobs] Digest (day) scheduling completed.
19/11 17:43 [170] - error: /login
 invalid csrf token
20/11 14:15 [170] - error: /login
 invalid csrf token
20/11 17:00 [170] - info: [user/jobs] Digest (day) scheduling completed.
20/11 22:26 [170] - error: /login
 invalid csrf token
21/11 07:02 [170] - error: /login
 invalid csrf token
21/11 11:42 [170] - error: /login
 invalid csrf token
21/11 11:43 [170] - error: /login
 invalid csrf token
21/11 17:00 [170] - info: [user/jobs] Digest (day) scheduling completed.
21/11 19:13 [170] - error: /login
 invalid csrf token
21/11 19:51 [170] - error: /logout
 invalid csrf token
21/11 19:51 [170] - error: /logout
 invalid csrf token
21/11 19:52 [170] - warn: Flooding detected! Calls : 101, Duration : 4962
21/11 19:52 [170] - warn: [socket.io] Too many emits! Disconnecting uid : 0. Events : topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet
21/11 21:03 [170] - error: /login
 invalid csrf token
21/11 21:04 [170] - error: /login
 invalid csrf token
21/11 21:05 [170] - error: /logout
 invalid csrf token
21/11 21:05 [170] - error: /logout
 invalid csrf token
22/11 08:18 [170] - error: /api/post/upload
 invalid csrf token
22/11 08:18 [170] - error: /api/post/upload
 invalid csrf token
22/11 08:49 [170] - error: /logout
 invalid csrf token
22/11 10:04 [170] - error: /login
 invalid csrf token
22/11 10:10 [170] - error: /login
 invalid csrf token
22/11 10:10 [170] - error: /login
 invalid csrf token
22/11 11:23 [170] - error: /login
 invalid csrf token
22/11 11:26 [170] - error: /login
 invalid csrf token
22/11 17:00 [170] - info: [user/jobs] Digest (day) scheduling completed.
23/11 17:00 [170] - info: [user/jobs] Digest (day) scheduling completed.
24/11 07:47 [170] - warn: Flooding detected! Calls : 101, Duration : 9185
24/11 07:47 [170] - warn: [socket.io] Too many emits! Disconnecting uid : 0. Events : topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet,topics.loadMoreFromSet```

Any ideas?

@pichalite Problem is in Persona theme, not NodeBB itself.

@pichalite It could be problem with Persona theme. I'm using version 1.1.2, files I had in mind are located in [nodebb install directory]/public/templates/partials/modals, but I can't seem to find them on Github. I've fixed it on my side but I would also like to contribute these fixes to public repository if they weren't fixed already.

I noticed that some modals are using hardcoded strings in v1.1.2. Is it still the same in newer versions?

Can you rephrase the question?

Extract all data for one user:
example on this forum: https://community.nodebb.org/api/user/egut

Deleting a user:
Write API plugin
https://github.com/NodeBB/nodebb-plugin-write-api

@MJ Try limiting category only to certain user group (example: admins or moderators).

@alff0x1f said in So Is NodeBB stable?:

I think its stable. I use it in production.

Same here. Done a lot of customization and no problems so far, using version 1.1.2 for now.

I've successfully customized email templates, but I still haven't found a way to change date format in email subject.
I'm using v 1.1.2 and current date format is "yyyy/mm/dd" and I want to change it to "dd/mm/yyyy".

Sorry for necromancing.

I'm in need of similar feature. Is anyone from nodeBB team willing to push me in the right direction? Perhaps @julian? If solution would be good enough I'm prepared to open source it (PR on Github).