401 Unauthenticated with valid api tokens #5580
Replies: 8 comments 6 replies
-
So, it looks like you can reach Firefly III, the network's working, it just tells you the token is invalid. Why are you running PHP 8.1 instead of 8.0? It shouldn't matter, but still. |
Beta Was this translation helpful? Give feedback.
-
i have the same problem when i try to log in with the firefly iii importer with the token i get this error. Yunohost 11 under Debian 11 |
Beta Was this translation helpful? Give feedback.
-
Same thing happens to me for some reason. That's strange because it was working at some point I even imported data. |
Beta Was this translation helpful? Give feedback.
-
I’m having this issue too. Every couple days, I get the error and create a token and it works. Then repeat |
Beta Was this translation helpful? Give feedback.
-
(TLDR: for me, generating a new token and then restarting the firefly container worked) I am also having this issue. I didn't touch my firefly docker-compose install (using personal token for importer) since May. Now I fired it up again and the importer can't connect. Have since tried:
result is the same: 401 error. I am stuck for now, any suggestion would be much appreciated! Edit: I found that a restart of the firefly container (not just the importer container) was needed for the new token to work. |
Beta Was this translation helpful? Give feedback.
-
I was similarly getting the 401, but I believe it was as a result of an improperly formatted request. Sort of like a fallback error. The server I have assembling the payload to POST to firefly was running into an exception when creating the In short, the request had the correct headers, URL, and could reach the firefly server, but was getting 401 back strictly based off the After fixing the server handling for the |
Beta Was this translation helpful? Give feedback.
-
I got this issue when booting up an old docker-compose Firefly III project (last used in May 2022), that I'm pretty sure worked with the Data Importer back then. My versions were 5.7.6 (Firefly III) & v0.9.9 (data importer). I tried creating a new Personal API token, clearing cookies, restarting containers, to no avail. Finally I upgraded the containers to the latest version (v6.1.6 & v1.4.1), which seems to have gone well out-of-the box, and also fixed the authentication issue. |
Beta Was this translation helpful? Give feedback.
-
I have the same issue but a new token and restarting the importer and the firefly pod as @SanderVocke suggested did not work for me. I cannot even use a new Token with a Curl request but it did work for me in the past. I switched over to Oauth and set the vanity URL and it's working for me now. This is of course more a workaround than a fix. |
Beta Was this translation helpful? Give feedback.
-
Support guidelines
I've found a bug and checked that ...
Description
I have followed the install guides and setup a new vm and deployed firefly iii via ansible
Then I went on to try and play around with it on my local network, but didn't get the importer nor the api to work properly.
I tried to get the importer to run using both a token and the oauth as specified on the guide, with oauth it asks for me to authorize the importer but then both converge on the same problem.
The api always ends up responding:
Probably related to: #5490
Expected behaviour
Importer / api authetication should work
Debug information
Debug information generated at 2022-01-21 00:15:37 Europe/Madrid for Firefly III version 5.6.10.
Steps to reproduce
Additional info
No response
Beta Was this translation helpful? Give feedback.
All reactions