• Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About FunnyPocketBook

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @mattie112 I saw the changes but I'm on vacation/without a computer until tomorrow, so I couldn't update the template yet. Will do as soon as I come back though!
  2. The data loss here is actually my fault, nothing you could have done if you aren't always reading the release changes of Firefly. I misread the changelogs for an update back in... October? I think and didn't adjust the container paths accordingly in the template
  3. Did you change the container path for UPLOAD_PATH to /var/www/html/storage/upload and after restarting upload the files? You have to do that, otherwise the files won't be stored in /mnt/user/appdata/firefly-iii/upload/
  4. Hey @Camilo It sounds like you had a < 5.4.0 version installed before you updated to the new version. The container path for newer versions for UPLOAD_PATH is `/var/www/html/storage/upload` instead of `/var/www/firefly-iii/storage/upload`. Updating to a newer version without updating the path may result in a data loss. You should check your host path `/mnt/user/appdata/firefly-iii/upload/` if the old attachments are still there. If they are, make a backup of them and then update the UPLOAD_PATH to `/var/www/html/storage/upload`. This should preserve your previously uploaded attach
  5. V1 isn't supported anymore, which is why I set the default layout to V2.
  6. @40foot Can you check the container logs and the browser console for any errors? Also, did you already try readding the docker image?
  7. Did you also make sure that the user firefly has the needed privileges for the database?
  8. Did you create the firefly user and set a password?
  9. Change the repository to jc5x/firefly-iii:beta instead of jc5x/firefly-iii
  10. Pretty much! If you have attachments, make sure to also save the APP_KEY environment variable.
  11. Have you followed this step already? Also, meinnamehier reported that the same issue got fixed after an array restart or a reboot.
  12. It appears that the Firefly-III CSV Importer saves the URI somewhere internally and doesn't look at the environment variable anymore once it's set. When I changed the URI to something invalid, it still pointed to the old, correct URI. In the CSV Importer WebUI, have you already clicked "Reauthenticate"? Clicking that fixed the issue for me.
  13. Hm, I have only ever experienced this behaviour when I had duplicate containers that were using different templates. Go to the console of the CSV importer and execute printenv, that shows you the environment variables of the container. Does the variable FIREFLY_III_ACCESS_TOKEN show up? Is the FIREFLY_III_URI correct?
  14. @meinnamehier I assume Firefly doesn't run on port 8080? What did you set FIREFLY_III_URI to, can you send a screenshot of your config? It could also be that you have tried to install the CSV Importer multiple times and are now stuck with multiple templates. Check if /boot/config/plugins/dockerMan/templates-user lists more than one CSV Importer and if so, you can remove the template that you don't want.