Lost all my data ? Help please

julian

If you had Redis persisting to disk, it would be at /var/lib/redis.

It sounds like someone (or some script, rather) is going around trying to connect to port 6379, and if successful, flushing the database.

Better use AUTH and have good backups!!

julian

@kacemlight This seems to be the case. I am able to connect to the redis server at nodejsworld.com:

$ redis-cli -h nodejsworld.com
nodejsworld.com:6379> keys *
1) "sess:0d5qvchIPxvQ-lsGNTJkWL7s1SQBrd8v"
2) "ip:recent"
3) "schemaDate"

Please take a look at this topic: http://redis.io/topics/security.

I realise this is a very rough time for you, @kacemlight, as you've lost your site data. I have every confidence that you will be more careful in the future and utilise backups in addition to setting up authentication for your database.

Robert

@julian Always a posibility too be honest. I'll have some fun opening my Redis port tonight to my server. Not like I have critical data on there anyways.

julian

@Kowlin I've found the easiest way is to just use ufw. If you only connect from one PC, then disallow requests from all IPs except your own, and set the default behaviour to DENY.

Robert

Well am I the only one a bit troubled about the fact that the default Redis security is so easy to avoid. I opened my Redis port from my router and connected to it without any single problem...

scottalanmiller

@kacemlight said:

Is someone here can explain me where to find if I have a backup.. How can I just lose all my data without a reason ?? Please someone explain me what's could have happened to my website ? I lose a nine months of hard work !!!

What's command I have to execute to try restoring my datas ?

Did you take a backup of any sort?

bitspook

@julian @Kowlin Redis is that bad? Did not know that. Planned on migrating to Mongodb before production anyway

Robert

@bitspook Like @julian said, security is retentively easy. But I'm surprised and scarred that its so weak by default. If it wasn't for my router I think my databases also could have been dropped.

scottalanmiller

@kacemlight said:

Is someone now why this happen ?!! Is it can be related to the hosting provider Digitalocean ?

That would not make any logical sense. DO is only your IaaS platform and does not touch the system itself. You would not suspect a hardware vendor in a physical deployment of deleting your database.

julian

@Kowlin said:

Well am I the only one a bit troubled about the fact that the default Redis security is so easy to avoid.

IIRC the default Redis config is "bind to 0.0.0.0", which means open to everyone. Might be the same with Mongo.

However, Ubuntu locks these configs down by binding to localhost only, so installing via apt-get is usually better than installing by downloading and compiling on your own.

scottalanmiller

@Kowlin said:

Well am I the only one a bit troubled about the fact that the default Redis security is so easy to avoid. I opened my Redis port from my router and connected to it without any single problem...

That is expected. That means that the firewall is open on your OS (is the firewall running?) and Redis does this because it is designed to be in a cluster and would need the port open to talk to itself or to a Sentinel.

bitspook

@julian said:

It sounds like someone (or some script, rather) is going around trying to connect to port 6379, and if successful, flushing the database.

maliciously?

julian

@bitspook Probably.

Looks like antirez added a large warning block about it here, and it may be uncommented by default now...
https://github.com/antirez/redis/blob/unstable/redis.conf#L40-L61

hek

Just bind redis to localhost. Then it's won't be accessible from the outside world.
By default redis listens to all interfaces which means all external ips (unless you have some firewall in place).

/etc/redis/redis.conf:

add
bind 127.0.0.1

Edit: Damn @julian you beat me.

Robert

@julian If this doesn't happen can we atleast add a warning to the NodeBB documentation for this?

kacemlight

Please if we supposed the backup was actived by default, how can I find the dump.rdb ? or maybe how can I check if it's activated ? I just want to be sure that there is no hope to get back my website. That's mean I lost nine months of work and now I will give up and stop hosting it...

julian

@Kowlin said:

@julian If this doesn't happen can we atleast add a warning to the NodeBB documentation for this?

I did amend the Ubuntu installation documentation yesterday to use Mongo instead. May as well.

scottalanmiller

@kacemlight said:

Please if we supposed the backup was actived by default, how can I find the dump.rdb ? or maybe how can I check if it's activated ? I just want to be sure that there is no hope to get back my website. That's mean I lost nine months of work and now I will give up and stop hosting it...

What backup would that be? if you didn't set it up, there is no backup. If you did, you would likely know where it was.

Do this... find / -name dump.rdb

Doubt that you are going to find anything, but only takes a minute to be sure.

scottalanmiller

@Kowlin said:

@julian If this doesn't happen can we atleast add a warning to the NodeBB documentation for this?

That people need to have firewalls? Seems a bit extreme to have to document in NodeBB's docs.

hek

@kacemlight

You have to create your own redis backup script that rotates/saves dump files. By default redis does not make any incremental and or multiple save files.

So if someone connect to your redis instance and do ```flushall`` your database will be gone again. Because the empty db get saved to disk in a few minutes (overwriting your old save-file).