Skip to content

Migration from v0.X to v1.X

Warning

Migrating to V1.X will impact (any change you made will be lost and must be adapted to the new configuration) :

  • Database model : your existing database will be lost, a new one will be created in the V1.

  • Crowdsec-agent configuration :

    • /etc/crowdsec/config/default.yaml : check new format
    • /etc/crowdsec/config/profiles.yaml : check new format

To upgrade Crowdsec from v0.X to v1, we'll follow those steps

Backup up configuration

sudo cscli backup save /tmp/crowdsec_backup
sudo cp -R  /etc/crowdsec/config/patterns /tmp/crowdsec_backup

Uninstall old version & install new

Download latest V1 Crowdsec version here

tar xvzf crowdsec-release.tgz
cd crowdsec-v1*/
sudo ./wizard.sh --uninstall
sudo ./wizard.sh --bininstall

Warning

Don't forget to remove metabase dashboard if you installed it manually (without cscli).

Restore configuration

Warning

Before restoring old backup, if you have local or tainted postoverflows, be aware that they are no longer compatible. You should update the syntax (the community and us are available to help you doing this part).

sudo cscli hub update
sudo cscli config restore --old-backup /tmp/crowdsec_backup/
sudo cp -R /tmp/crowdsec_backup/patterns /etc/crowdsec/

Start & health check

Finally, you will be able to start Crowdsec service. Before that, just check if local API (LAPI) and API are correctly configured.

ubuntu@ip-:~$ sudo cscli lapi status 
INFO[0000] Loaded credentials from /etc/crowdsec/local_api_credentials.yaml 
INFO[0000] Trying to authenticate with username 941c3fxxxxxxxxxxxxxxxxxxxxxx on http://localhost:8080/ 
INFO[0000] You can successfully interact with Local API (LAPI)

ubuntu@ip-:~$ sudo cscli capi status 
INFO[0000] Loaded credentials from /etc/crowdsec/online_api_credentials.yaml 
INFO[0000] Trying to authenticate with username 941c3fxxxxxxxxxxxxxxxxxxxxxxx on https://api.crowdsec.net/ 
INFO[0000] You can successfully interact with Central API (CAPI)

ubuntu@ip-:~$ sudo systemctl start crowdsec.service
ubuntu@ip-:~$ sudo systemctl status crowdsec.service

You can even check logs (located by default here: /var/log/crowdsec.log & /var/log/crowdsec_api.log).

You can now navigate documentation to learn new cscli commands to interact with crowdsec.

Upgrade bouncers

If you were using bouncers (formerly called blocker(s)), you need to replace them by the new compatibles bouncers, available on the hub (selecting agent version to v1).

Following your bouncer type (netfilter, nginx, wordpress etc...), you need to replace them by the new available bouncers on the hub, please follow the bouncers documentation that will help you to install easily.

We're also available to help (on discourse or gitter) upgrading your bouncers.