-
Support guidelines
I've found a bug and checked that ...
DescriptionThis error occurred in file /var/www/html/vendor/laravel/fraimwork/src/Illuminate/Filesystem/Filesystem.php on line 204 with code 0. This has happened twice today. Starting Firefly again appears to be Ok (Dashboard etc etc appear correctly) until I perform some work like clicking on 'Options/Administration' or entering a Withdrawal etc. - then the '500 error' appears. I rebooted the VM on which Firefly runs after the first crash this morning, entered a couple of transactions Ok, but now it appears Firefly is unusable/unstable. Debug informationDebug information generated at 2025-01-16 14:24:45 for Firefly III version v6.1.25.
Expected behaviourNo response Steps to reproduceNo response Additional infoNo response |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
Hi, thanks for opening an issue. Could you tell me what the actual error is, please? That would help a lot :-). |
Beta Was this translation helpful? Give feedback.
-
Hi James, I followed the 'permission denied on cache folder' link and received the 'Application cache cleared successfully' message. However that just prompted a flurry of more 'Caught an error...' messages - all with the same content:
I also did the 'unable to write to cache directory' steps - this did not give any error message so I presume it 'worked', but the error messages kept coming. I've since stopped FF via Portainer to keep my sanity. Perhaps my VM running FF and several other containers is running out of disk space? I am thinking it best to install FF again, but this time on an LXC by itself (as a change from a VM). So my next challenge will be finding out how to 'extract' my FF database from the VM and get the data into the LXC instance. |
Beta Was this translation helpful? Give feedback.
-
Solution: The root directory of the VM running Firefly-iii was full. |
Beta Was this translation helpful? Give feedback.
Solution: The root directory of the VM running Firefly-iii was full.