-
Support guidelines
I've found a bug and checked that ...
DescriptionWith the start of 2025 I added a new token since the old one expired. I updated the new token in the docker compose and restarted the containers. FF3 starts as expected and is accessible. The importer see's the token, but is unable access FF3. Multiple tokens have been created and tried, but importer can not connect. Debug informationDebug information generated at 2025-01-11 16:16:05 Europe/Amsterdam for Firefly III Data Importer version 1.5.7.
Expected behaviour
Steps to reproduce
Additional infoNo response |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 4 replies
-
Hey, thanks for opening an issue. Are you using the web interface to use the data importer after you changed the token? |
Beta Was this translation helpful? Give feedback.
-
Yes, Updated the token, restarted the containers and then i'm accessing the web interface for the FF3 importer. It's issuing this message:
|
Beta Was this translation helpful? Give feedback.
So just figured it out, but don't know what changed. I had to change the IP to the internal docker network 172.x.x.x:8080, vs using the external mapped IP of the server:port, 192.168.x.x:9005.
Was there some code change restricting the usage of the serverIP:MappedPort?