Getting started

Firefly III not working: a checklist for self-hosted users

Firefly III not working? Check the server, database, update and browser cache in order, protect your data first, and reconcile the balance afterwards.

Editorial illustration for Firefly III not working: a checklist for self-hosted users

When Firefly III stops working, the cause is usually one of four things: the server it runs on is down, the database behind it cannot be reached, an update changed something, or your browser is showing a stale page. Test them in that order before you reinstall anything, and do not delete any data folder while you are guessing.

Is it the page, the server or the data?

A self-hosted finance tool is really three pieces stacked together: the machine or hosting plan, the program that serves the pages, and the database holding your entries. A fault in any layer looks the same from your chair, a blank page or an error message. The trick is to find which layer is failing before you change anything.

  • If other things on the same machine or hosting plan also fail, the problem is the server, not the finance tool.
  • If the login page loads but saving fails, suspect the database or disk space.
  • If it broke right after an update, the update is the first suspect, and the release notes of the project are the place to read.
  • If it works in a private browser window but not in your normal one, clear the cache and cookies for that address only.

Checks to run, in this order

  1. Open the address from a second device or a mobile network. This tells you whether the problem is your own connection.
  2. Log in to your hosting panel or machine and confirm it is running and has free disk space. A full disk is a common reason for sudden failures.
  3. Look at the error log that your setup produces. Copy the last few lines into a note; you will need them if you ask for help in the project's community.
  4. Check that the database service is running and that the login details in your settings file have not changed.
  5. Only then think about rolling back the last update, and only after you have copied the data.

It opens, but the balance looks wrong. Now what?

Software that loads is not proof that your records are complete. After an outage, compare one account against your bank statement. Say your tool shows a closing balance of ₹41,300 and the statement says ₹43,800. The gap is ₹43,800 minus ₹41,300, which is ₹2,500. Sort both lists by date and look for a single entry of exactly that amount, a pair that adds up to it, or a repeated entry.

What you findWhat it usually meansWhat to do
One missing row of ₹2,500An entry was never saved, often because the outage hit mid-entryAdd it with the date from the statement
Two rows of ₹1,250 on the same dayAn import or a retry saved a duplicateDelete one after checking the statement shows only one
Gap that is not a round figureSeveral small entries are missingReconcile week by week until the gap closes

Should you keep running your own server?

Self-hosting gives you control, and for some people that is the whole point. It also gives you a small job: updates, backups and the occasional outage. Say the cheapest server you trust costs ₹500 a month. That is ₹6,000 a year before you count your own evenings, which is worth weighing against the value of what you track.

If the upkeep is the part you resent, a hosted tracker removes it. SpendixAI works from statements you upload as PDF, CSV or Excel, with rows reviewed before saving, so there is no server for you to maintain. It does not connect to your bank, and it is not a clone of every self-hosted feature, so look at the free plan before moving anything.

A routine that makes the next outage boring

  • Export or copy your data on a fixed day each month, for example the first Sunday.
  • Keep the last three copies and delete older ones.
  • Write down the update steps you used, so you can reverse them.
  • Once a quarter, reconcile one account against its statement even if nothing seems wrong.
  • Keep your bank statements themselves for the year; they are the record that outlives any app.
SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports