Bug: Login redirection loop on 404 error #270
Comments
|
Hey @csmith1210, Can you try to connect to https://demo.firefly-iii.org/profile with a PAT? If you can't, can you send my a screenshot of the error returned by Abacus when clicking If you can connect to |
|
Yeah so I don't have any issue on the demo site with a PAT token. Though I don't know what could be wrong because even setting up the app with the url as the local-ip:port (without any proxy or oauth) still has this redirect behavior. After some time, there is occasionally an error that says "A network error has occurred". Is there any way to grab the logs from the app? This is what the behavior looks like: |
|
It's some kind of redirection issue on the home screen, and since you only have one account, it tries to connect directly to it. (Something I should probably catch) Just checking, are you sure that your are running the latest version of FireflyIII? It must be something that abacus is trying to fetch and can't but the login process is working. |
|
I am having the same issue, just started a firefly instance to try it out. Here is the debug page of Firefly: `Debug information generated at 2024-05-06 02:59:28 America/Ensenada for Firefly III version 5.5.13.
|
|
@victorbalssa Saw your question regarding the latest version and saw I was running an older version that is the default deployment on CapRover that I'm playing around with. Updating to 6.1.15Firefly III © James Cole, AGPL-3.0-or-later instantly fixed the issue with Abacus. Probably should catch that or at least warn users to use e.g. 6.0+ version of Firefly. |
|
@jacobburrell Well it was nice to know I wasn’t the only one, but unfortunately I am running 6.1.15 already via docker. |
|
Same here, I'm also running 6.1.15 |
|
I'm going to remove the redirection loop in the next patch. It's related to this error catching when any Home screen API call return a abacus/src/components/UI/ErrorWidget.tsx Lines 40 to 42 in 4c36aa7 To help me reproduce this behaviour, here is the list you could try to see if any returns a
|
|
Just thinking of some quick fix, do you have |
|
I had it disabled, I enabled it but I'm still experiencing the same issue. |
|
Another try: Go to your FireflyIII instance backend here: Under "Home Screen" set a preference for home screen accounts to display. Click "Save Settings". |
|
Thank you, but the problem is still there. |
|
Ok can you share your access.log of FIII instance when the redirection loop happens? I'm trying to find out where the |
victorbalssa
changed the title
|
|
This is really the preference
Can you retry to save just 1 or 2 accounts on the |
|
Changing the Homescreen preferences does not have any effect for me either.
|
|
Aha! Going through the preferences API numerically I found that the call should actually be |
|
Arf good catch firefly-iii/firefly-iii@6189d24. I was still on the old version, it's still working for me (no 404) with But we have our answer, I will try/catch this error. |
|
If any more testing is required, I may be of assistance, as I am experiencing the same issue. I also have a containerized setup (rootless podman) behind HAProxy. |
Nonoe of them yield a 404. My firefly III is v 6.1.15, btw |
Describe the bug
I just installed a fresh F3 docker instance and am trying to connect the iOS app to it. Initially, my set up uses Traefik, Authentik with Referrer setup, and Cloudflare tunnel. I was able to get the app to log in with PAT after disabling CF rocket loader and email obfuscation (not sure if this was needed), and adding the api as an unauthenticated path in Authentik. However, the app bugs out and goes into a constant redirection loop to load the home page. I was unable to find any stand out traces in the logs of either traefik, Authentik, or F3. So I then tried to access the server locally without any middle man and I get the same result: constant redirection using PAT or OAuth. I am unable to reproduce this using the F3 demo site.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Log in and display homepage of app
Smartphone (please complete the following information):
Additional context
Here’s the urls that the app tried to access. I noticed a previous bug reported for the Android app where the currency was incorrect, but that don’t seem to be the case here.
The text was updated successfully, but these errors were encountered: