-
-
Notifications
You must be signed in to change notification settings - Fork 38
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: "Failed to validate AccessToken, please re-check your token or backend URL" #256
Comments
|
Hey @paulcalabro, Was PAT working before I'm also trying to narrow down the login issues others can have (#257): Can you try to connect to this demo instance: https://demo.firefly-iii.org/ ? it will help me determine if it's really Abacus Do you use the latest FireflyIII version? (6.1.9) Last thing, if you have access to an android, (if you can you replicate the same error on android)? Thanks |
Hey @victorbalssa, Here's the answers to your questions
I set up Burp Suite to act as a Proxy in between my phone and Firefly III. |
Thank you @paulcalabro, it will help me a lot, I suspect the last build to block some specific LAN traffic on IOS. |
Okay, I was able to resolve my issue! 🥳 For those experiencing the same issue, the tl;dr is I created a local CA, created a cert issued by that CA, and deployed the CA cert to my phone and computer. I then configured Traefik to use the cert issued by the CA. Helpful resources:
Sample
Things that the first link doesn't cover OTB:
So I think what's broken is the ability to NOT use TLS. |
This makes a lot more sense to me! 🎉 I will create a new version with the ability to use TLS AND unsecured Thanks again @paulcalabro 💯 |
Done in |
Describe the bug
Receiving the following error message when logging in using a Personal Access Token:
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Arrive at landing page
Screenshots
N/A
Smartphone (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: