I upgraded my 2.3.1 installation using composer, and everything seemed OK. I then saw I couldn't go to the web setup wizard, and got the white screen with the grey bar I'd heard so much about and is explained exactly and shown here: https://stackoverflow.com/questions/54411785/magento-2-install-setup-blank-page
After not finding anything in any error logs, I created a test site by unzipping the full release for 2.3.2 and creating a new db for it. As soon as I tried the install by visiting the site, a process I'd successfully been through many times before, I got the WSOD. I noticed the URL for this new site was example.com/setup, exactly the same as the one failing on the production site. Suspecting permission problems, I chmoded every file to +777, (something I'd never do in reality!) but it made no difference. However, there was a message in in the debug log - "Error: Application is not installed yet. [] []". Gosh, ain't that a head spinner - the install fails because it's not installed yet!!!
I know I could perform the full install with composer, but that won't help me fix the live system.
What gives please?
Ubuntu 18.04/PHP 7.2.19
Solved! Go to Solution.
It was set to files, so that isn't the problem.
I've followed through the many, many reports and possible fixes to this from the thread you mentioned and still got nowhere.
In my experience (just check my postings here on this forum) each new release does fix some things but introduces more problems.
I have a solution to this when it occurs after the upgrade to 2.3.3. I haven't tested a new install, but after the upgrade to 2.3.3 I found logging into admin caused the error reported here: https://mage2.pro/t/topic/5986
The "fix" to that is described here, which is to basically delete and recreate the admin user, which works but also had the nice side effect of fixing the white screen issue I originally reported.
Hello @bdamage
Check your app/etc/env.php and look for 'session' => [
'save' =>
Is this standing on files or on db ?
If setting is db change it to files works.
Or follow this link if it can help you:
https://github.com/magento/magento2/issues/19491
It was set to files, so that isn't the problem.
I've followed through the many, many reports and possible fixes to this from the thread you mentioned and still got nowhere.
In my experience (just check my postings here on this forum) each new release does fix some things but introduces more problems.
I have a solution to this when it occurs after the upgrade to 2.3.3. I haven't tested a new install, but after the upgrade to 2.3.3 I found logging into admin caused the error reported here: https://mage2.pro/t/topic/5986
The "fix" to that is described here, which is to basically delete and recreate the admin user, which works but also had the nice side effect of fixing the white screen issue I originally reported.