-
-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Blank homepage after Debian update #2748
Comments
Make sure your webserver is running PHP 7.3, and run |
Thanks for your help. I have PHP 7.3.9 and the config in the .env file looks fine. I've ran
After this I tried to connect to see if this solved the problem anyway and I got a 404 error. After some investigation I found out that I don't have the "public" folder inside "firefly-iii". I don't know if my Apache config was right, but previously I got it working bi setting the document root to /var/www/firefly-iii/public but this doesn't work anymore. Should I reinstall firefly or there is something else I should try? |
A quick try at retrieving the "public" folder from this repo didn't work. Since there is a new release of Firefly-III, I'm reinstalling now to fix the problem and get the new version at the same time. |
I am running Firefly III version 4.8.1.4
Description
I was able to setup Firefly III and get to the point where I could reach the registration page via browser, but didn't registered any account yet. I left it as it was for some days, then four days ago I updated some packages on my Debian installation and checked the home page again, but this time I got a blank page. I'm quite sure that this is not caused by my Apache config (did some tests). In firefly's log folder I found two files, the one with the date of that day is called "ff3-apache2handler-2019-10-15.log" and contains the following error
repeated a few times. If you need it here is a pastebin of the full log: https://pastebin.com/T2z8nzDu. My understanding is that I'm missing a library, but I don't know which one.
Thanks for your help.
Extra info
Although I think the Debian update s the most likely cause I can't be sure it was the update fault because:
Bonus points
The text was updated successfully, but these errors were encountered: