I'm using nginx with SSL, had the same issue with login/CSRF Token when migrated from 1.0.3 to 1.1.2, and, as described before but always good to remain, adding this to my nginx config (/etc/nginx/sites-enabled/default in my case) saved my life, thank

proxy_set_header X-Forwarded-Proto $scheme;

@charles
Perfect, thanks

@rod,
thank, that's the auto tree ?

Guys,

I just upgraded from 1.0.0 to latest (Control panel told me new version 1.0.1-auto0) so I did

./nodebb stop
git fetch
git reset --hard origin/v1.x.x
./nodebb upgrade #(could take up to 5 min)
./nodebb start

Now control panel tells me I'm on V1.0.2 all is fine

@julian
Sorry forgot this one, mail notification settings says
"Send an email if a new chat message arrives and I am not online"
And I receive one even if I'm connected (but not on same tab) which does not match option configuration

@julian
that makes sense, but from my point of view (user view) the way it worked before was much efficient, let me explain :
when I was connected with browser but not on the same tab I was hearing sound notification and number in square red on the nodebb tab was increasing, so easily I selected nodeBB tab to do response and get back to another working tab that was simple and easy
Today even if I'm connected but not on tab I'm totally spammed by mail on response. And when I'm on nodeBB tab, I get notification from message I received before I was on this tab, but as I'm now on node BB Tab, why I'm notified ?

To be simple, when I'm chatting and doing other thin in same time, I see conversation + Conversation notification I've already seen + mail notification, just sometime amazing

It could be interesting how other chat users feels on this ? but trust me, guys I'm talking with on chat feel the same way

Hi there,
since version V0.9.0 I noticed two strange things with chat that I didn't had before (on my own server)

• even if I'm connected (but nodebb tab on browser is not the active one) on nodebb, sometime I receive the mail notification
• the 2nd is that I receive notification popup (bottom right on browser screen) 2/3 min after the message is displayed on my screen, so I've already read it

Is it just me ?

thanks

What's amazing is that happening to several people in the same days interval on different redis version and nodeBB version without touching anything from days !!!

I've backup up also every hour now !!!

crontab - e then add

# 0 5 * * 1 tar -zcf /var/backups/home.tgz /home/
#
# For more information see the manual pages of crontab(5) and cron(8)
#
# m h  dom mon dow   command
MAILTO=""
13 * * * *  /root/redis-backup.sh

And /root/redis-backup.sh (grabbed from Internet, don't remember where and modified to fit my needs).

dont forget to chmod ug+x /root/redis-backup.sh

#!/bin/bash
#
## redis backup script
## usage
## redis-backup.sh port backup.dir

port=${1:-6379}
backup_dir=${2:-"/var/lib/redis/backup"}

cli="/usr/bin/redis-cli -p $port"
rdb="/var/lib/redis/dump.rdb"

test -f $rdb || {
  echo "[$port] No RDB Found" ; exit 1
}
test -d $backup_dir || {
  echo "[$port] Create backup directory $backup_dir" && mkdir -p $backup_dir
}

# perform a bgsave before copy
echo bgsave | $cli
echo "[$port] waiting for 5 seconds..."
sleep 5
try=10
while [ $try -gt 0 ] ; do
  ## redis-cli output dos format line feed '\r\n', remove '\r'
  bg=$(echo 'info Persistence' | $cli | awk -F: '/rdb_bgsave_in_progress/{sub(/\r/, "", $0); print $2}')
  ok=$(echo 'info Persistence' | $cli | awk -F: '/rdb_last_bgsave_status/{sub(/\r/, "", $0); print $2}')
  if [ "$bg" = "0" ] && [ "$ok" = "ok" ] ; then
    dst="$backup_dir/$port-dump.$(date +%Y%m%d%H%M).rdb"
    cp $rdb $dst
    if [ $? = 0 ] ; then
      echo "[$port] redis rdb $rdb copied to $dst."

      # delete rdb created 30 days ago
      cd $backup_dir
      find . \( -name "$port-dump*" \) -mtime +30 -exec rm -f {} \;
      exit 0
    else
      echo "[$port] >> Failed to copy $rdb to $dst!"
    fi
  fi
  try=$((try - 1))
  echo "[$port] redis maybe busy, waiting and retry in 5s..."
  sleep 5
done

If it can help, it can be better and not in root folder, done in a hurry, you know what I mean

I had back this problem a 2nd time 2 days ago, I don't know if it's related but I was doing iptables FW settings on the VM, I had nodeBB running, and also redis and from my computer desktop redis desktop manager connected to DB.
Then I made a mistake in iptables, blocked all redis port (even local), saying nodebb unable to connect to redis (so as redis desktop manager) then when I openned back 6379 port, all data was gone, not sure if it's related, just an information.

Of course,

WP 4.3.1 , by opening an issue, you mean new post on support of nodebb or on github for plugins ?
not sure where to ask, sorry about this

yes, with this one can't create the topic after blog post but works once link from WP and nodeBB created by hand on the database

root# npm ls nodebb-plugin-blog-comments
[email protected] /usr/local/share/nodebb
└── [email protected]  extraneous

@psychobunny
which version you want me to test ?

Yeah I've already put a backup into /etc/cron.hourly as a fix

I'll check this thanks

yeah no problem for me using AOF, I need to set it in redis.conf ?

after corruption I connected to redis without issue but database structure was

instead of

In my case it's saved every 5 minutes onto disk, so I should have lost only 5 minutes, except if as you says, it saved corrupted db.

297] 08 Nov 02:19:36.116 * Background saving terminated with success
[297] 08 Nov 02:24:37.088 * 10 changes in 300 seconds. Saving...
[297] 08 Nov 02:24:37.091 * Background saving started by pid 4508
[4508] 08 Nov 02:24:37.114 * DB saved on disk
[4508] 08 Nov 02:24:37.115 * RDB: 0 MB of memory used by copy-on-write
[297] 08 Nov 02:24:37.192 * Background saving terminated with success
[297] 08 Nov 02:29:38.091 * 10 changes in 300 seconds. Saving...
[297] 08 Nov 02:29:38.092 * Background saving started by pid 4511
[4511] 08 Nov 02:29:38.110 * DB saved on disk
[4511] 08 Nov 02:29:38.110 * RDB: 0 MB of memory used by copy-on-write
[297] 08 Nov 02:29:38.193 * Background saving terminated with success
[297] 08 Nov 02:34:39.034 * 10 changes in 300 seconds. Saving...
[297] 08 Nov 02:34:39.035 * Background saving started by pid 4514
[4514] 08 Nov 02:34:39.059 * DB saved on disk

@AOKP
I agree, upgrading to 3.0.5 will certainly not solve the issue, but does not hurt to try

correct, I forgot you had the issue

@Pilvinen
You said it all you've got a "dedicated server", I've got a VPS which is slightly different because all resources are shared with other customers VM (on same physical server), so of course in your case it make no sense, but in mine, I'm not sure this is so silly