Cloudron makes it easy to run web apps like WordPress, Nextcloud, GitLab on your server. Find out more or install now.

Firefly III

19 Topics 182 Posts
  • Firefly III - Package Updates

    0 Votes
    67 Posts


    Update Firefly-III to 6.0.26 Full changelog v2 index has better overview of bills (now called subscriptions) My attempt to build the v3-layout is now officially deprecated and removed. To see the new layout (in beta), use FIREFLY_III_LAYOUT=v2. Issue 7970 Bad redirect for mass edit/delete forms. Issue 7983 Bad math in the calculation of liabilities Issue 7973 Bad account validation broke certain imports Issue 7981 Menu had a bad link, thanks @Maxco10! Slack alerts now use the correct URL Better htaccess files thanks to Softaculous. Issue 7986, issue 7992 Fix exception when calling specific end points Issue 7990 Remove unused translations Change htaccess rules so certain files can't be accessed.
  • Data Importer Tool

    0 Votes
    10 Posts

    I'm using pretty much the standard, the default .htaccess that comes with the data-importer tool, and the generated .htpasswd file I created. I've just added the below. Just update the # Whitelist API Requests line with API requests from the services you're using with the data-import tool.

    # Password Protect Entire Directory AuthName "Restricted Access" AuthType Basic AuthUserFile /path/to/.htpasswd require valid-user # Whitelist API Requests Allow from
  • Monthly fees checklist or something :)

    0 Votes
    2 Posts

    @pawel-biskupski maybe you can ask this in the upstream forum -

  • API calls failing

    0 Votes
    3 Posts

    Does the latest package solve any of these issues?

  • 0 Votes
    5 Posts

    @girish thanks! It's working fine now.
    This is the reason why I love cloudroun ❤

  • 0 Votes
    6 Posts

    @nottheend thanks for the update! fixed the title as well.

  • Unable to use API for firefly-iii

    1 Votes
    5 Posts

    To support Bearer authentication with proxyAuth, I have added a new flag in the manifest called supportsBearerAuth . This will be available in 7.3. After that, the curl request works.

  • 0 Votes
    5 Posts

    @jordanurbs Which package version are you on ? It's listed in the Update section of the app.

    As it stands, if it doesn't find any users, it means there are no users in the database atleast. Are you first able to roll back to a working app and run the command to verify your user is still there?

    dbe09602d26c384d4b8308b70b72452423=> select email from users; email ---------------- (1 row)
  • Firefly III not updating

    0 Votes
    3 Posts

    Ok, thanks.

  • Importers?

    1 Votes
    14 Posts

    @colonelpanic thank you!!

  • Upstream dropped LDAP support with v5.7.0

    4 Votes
    9 Posts

    @infogulch said in Upstream dropped LDAP support with v5.7.0:

    Did you happen to check whether the x-forwarded-* headers are stripped from the original request? Theres a potential impersonation vuln if we're not careful with these headers in particular.

    Right... The headers are always set/cleared across all locations in the nginx proxy auth config. It's in our e2e tests as well (though they have not passed yet).

  • Error! Unauthenticated

    0 Votes
    10 Posts

    @girish Thank you very much!!

  • Unable to login after upgrade to Firefly III 5.6.10

    0 Votes
    12 Posts

    @girish - that did the trick. I upgraded to 2.3.0-1 and I can log in as before.

  • Not up-to-date?

    0 Votes
    2 Posts

    The main reason is that their rewrite of the LDAP connector does not work anymore and is pending fixes. I had some attempts to contribute a fix, but I so far lack the in-depth knowledge of the PHP frameworks used. It is still on my list to hopefully be able to contribute a fix. You can track the upstream issue at

  • CRON Help

    0 Votes
    5 Posts

    I have added a note in the docs and in the UI as well.

  • 0 Votes
    3 Posts

    Oh looks like you reported it already at . But it seems you are not running Cloudron at all. This is a forum for apps installed using Cloudron and not a general app support forum for Firefly III. The github issue tracker is the correct place.

  • 1 Votes
    2 Posts

    @hillside502 done!

  • How to create a OAUTH2 client ID - Secret ?

    0 Votes
    15 Posts

    This is issue is now fixed ! thanks a lot !!! 🙂


  • Firefly III without LDAP?

    2 Votes
    4 Posts

    Right now with cloudron, some apps supports LDAP, some don't.

    If I need to do a cloudron setup comprising apps that are all LDAP, I of course use LDAP in order to get one login to rule them all.

    But if I do a cloudron setup where an app is not LDAP, I prefer to have all app not using LDAP.
    It's confusing to have to explain to people that for those X apps, you need to use the same login, but for those X apps, it's separate logins, even though it's all based on the same main domain.

    That's why I prefer to have both LDAP and non LDAP version of an app available.

    In the case of Firefly, I think LDAP is even less useful, because it's personal finance and probably less useful in an organization context. For example, if I want to give a Firefly instance for a friend, I don't need to have an additional LDAP user. I'd prefer to have the friend has its own login with the app.