Firefly III has a recurring transactions option. In order for that to work, you need to setup a cronjob. Without that, you get an error at the top of the page saying:

It seems the cron job that is necessary to support recurring transactions has never 
run. This is of course normal when you have just installed Firefly III, 
but this should be something to set up as soon as possible. Please check 
out the help-pages using the (?)-icon in the top right corner of the page.

Firefly III has an API to which you make a get request that triggers recurring transactions update. API call URL is:


To generate a token, go to your Firefly GUI -> Options -> Profile -> Command line token and copy token to URL.



If you go to this URL now, your Firefly will run recurring transactions. Because we don’t want to do that manually, we will do it via cronjob that will run every day at 3 AM.

You can do it on any Linux box with normal cronjob:

crontab -e

and add this line:

0 3 * * * http://firefly.example/api/v1/cron/6c57c098904f6f4765b52a4bc493687p

Because we are running Firefly 3 in Docker, more neat option is to add Alpine linux image to our docker compose and run it along within stack:

version: '3.3'

    image: fireflyiii/core:latest
    restart: always
      - firefly_iii_upload:/var/www/html/storage/upload
    env_file: stack.env
      - 8080:8080
      - db
    image: mariadb:10.8.2
    hostname: fireflyiiidb
    restart: always
      - MYSQL_USER=firefly
      - MYSQL_PASSWORD=secret_firefly_password
      - MYSQL_DATABASE=firefly
      - firefly_iii_db:/var/lib/mysql
     image: alpine
     command: sh -c "echo \"0 3 * * * wget http://firefly.example/api/v1/cron/6c57c098904f6f4765b52a4bc493687p\" | crontab - && crond -f -L /dev/stdout"

After the stack is running, enter a shell of your Alpine container and check if cronjob is present:

crontab -l

Had some issues with Cisco DNAC and Stealthwatch. After settings up Stealthwatch server and Netflow collector, some of SDA devices were not compatible with Stealthwatch. The reason was: “NBAR is enabled on this device“. In DNA center, NBAR and CBAR was actually disabled, but the problem stil persisted. CBAR and NBAR were previously enabled, but after disabling it, it did not clean all devices. Guess this is a “cleanup” bug in DNA center. Solution was to manually remove ip flow from affected devices.

DNA center version:

Screenshot of affected devices:

Solution: Clear ip flow from all interfaces on affected device, and resync device in DNA center.


conf t
int range gi1/0/1-48,Te1/1/1-4,Gi1/1/1-4
no ip flow monitor dnacmonitor input
no ip flow monitor dnacmonitor output

Go to DNA center, Inventory -> Select device -> Actions -> Inventory -> Resync device

Wait couple of minutes, and you should be able to enable Stealthwatch for this device.