@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;
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
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.
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.