Replies: 2 comments
-
Hey, thanks for starting this discussion. This usually happens when you have an old database volume still lingering around. They get locked to one IP so if that is the old one, that's what causes the error. Delete all containers AND volumes, and it should run as expected. Cheers, |
Beta Was this translation helpful? Give feedback.
0 replies
-
Hi, I just deleted everything and set it up again and it works now. Again thank you very much. Cheers |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
I just tried to setup a Firefly III Docker stack with Portainer as explained in the documentation. I used the provided docker compose and stack.env file and I changed the mentioned values. I did customize it to my needs. I changed the ports from the firefly-core and importer container. You can find my compose and stack.env files attached.
compose.txt
stack.env.txt
Since I am running this stack on my RaspberryPi am unsure about:
FIREFLY_III_URL=http://app:8080
VANITY_URL=http://localhost
Maybe someone can explain these two values to me. Right now I get nowhere with them. The comments at the top of the compose file are also no help for me.
The stack deploys correctly. When entering the webpage of the firefly core container I am greeted with the following error message:

Host 172.21.0.4 is the firefly_iii_core container
I already tried to fix it with solutions from other posts here with similiar problems but nothing worked. I hope someone here is kind enough to help me out.
Thanks
Beta Was this translation helpful? Give feedback.
All reactions