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


Skip to content

Firefly III

20 Topics 208 Posts
  • Firefly III - Package Updates

    Pinned
    82
    0 Votes
    82 Posts
    3k Views
    nebulonN

    [3.5.2]

    Update Firefly-III to 6.1.15 Full changelog Issue 8812 (Login with AUTHENTICATION_GUARD=remote_user_guard fails due to missing UserGroup) reported by @nebulade You may have to define again which asset accounts you want to see on the dashboard. Sorry about that. Expanded some database models. Limit the number of error messages Firefly III will send (so Mailgun keeps liking me). PR 8746 (Set date to now when cloning journal) reported by @imlonghao Issue 8748 (Release tarballs mistakenly include the .zip artifact) reported by @sudoBash418 Discussion 8750 (API To change transaction fails to find destination_id) started by @soloam Issue 8779 (Change Password Form not working ≥ 6.1.11) reported by @jemtz-deleon Issue 8781 (Bill information missing in /api/v1/search/transactions responses) reported by @daanvanberkel Issue 8752 (Transactions reorder not work (error 404)) reported by @BoGnY Issue 8613 (Some minor color issues) reported by @rumpff Issue 8776 (report-data/category/expenses has wrong sums with specific date range) reported by @bouil
  • Data Importer Tool

    17
    0 Votes
    17 Posts
    552 Views
    J

    @dadams-AU More than likely along the lines of what @robi said.

    You'll need to retrace your steps and ensure you completed the configuration change in the public routes in /app/data/apache/app.conf and ensure that you set the permissions correctly using:

    sudo chown -R www-data:www-data /app/data/data-importer sudo chmod -R 775 /app/data/data-importer/storage

    If you haven't restarted the LAMP app, you'll need to do that before all of the previous settings work correctly.

  • 2 Votes
    4 Posts
    113 Views
    A

    Highly appreciated 🙏

  • Monthly fees checklist or something :)

    2
    0 Votes
    2 Posts
    106 Views
    girishG

    @pawel-biskupski maybe you can ask this in the upstream forum - https://github.com/orgs/firefly-iii/discussions

  • API calls failing

    3
    0 Votes
    3 Posts
    118 Views
    girishG

    Does the latest package solve any of these issues?

  • 0 Votes
    5 Posts
    224 Views
    nottheendN

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

  • 0 Votes
    6 Posts
    234 Views
    girishG

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

  • Unable to use API for firefly-iii

    5
    1 Votes
    5 Posts
    549 Views
    girishG

    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
    424 Views
    girishG

    @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 ---------------- mail@girish.in (1 row)
  • Firefly III not updating

    Solved
    3
    0 Votes
    3 Posts
    219 Views
    J

    Ok, thanks.

  • Importers?

    14
    1 Votes
    14 Posts
    1k Views
    jagadeesh-s2104J

    @colonelpanic thank you!!

  • Upstream dropped LDAP support with v5.7.0

    9
    4 Votes
    9 Posts
    609 Views
    girishG

    @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

    10
    0 Votes
    10 Posts
    526 Views
    nottheendN

    @girish Thank you very much!!

  • Unable to login after upgrade to Firefly III 5.6.10

    Solved
    12
    0 Votes
    12 Posts
    516 Views
    colonelpanicC

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

  • Not up-to-date?

    2
    0 Votes
    2 Posts
    190 Views
    nebulonN

    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 https://github.com/firefly-iii/firefly-iii/issues/5133

  • CRON Help

    5
    0 Votes
    5 Posts
    437 Views
    girishG

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

  • 0 Votes
    3 Posts
    233 Views
    girishG

    Oh looks like you reported it already at https://github.com/firefly-iii/firefly-iii/issues/4960 . 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.

  • Security vulnerability fixed in 5.5.12 --- out upstream

    Solved
    2
    1 Votes
    2 Posts
    219 Views
    girishG

    @hillside502 done!

  • How to create a OAUTH2 client ID - Secret ?

    Solved
    15
    0 Votes
    15 Posts
    579 Views
    rmdesR

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

    Screenshot.png

  • Firefly III without LDAP?

    Moved
    4
    2 Votes
    4 Posts
    308 Views
    ruihildtR

    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.