Site broken after upgrade about trellis

[swalkinshaw]

Did you re-provision the box after the upgrade? If files have changed, the playbook would need to be re-run.

And if there's a white screen, there's an error somewhere that can be found in a log file.

[mAAdhaTTah]

Re-provisioned and no change. Nothing in the nginx error logs stored in /srv/www/sitename.tld/logs that seem to point to anything. There also doesn't appear to be any errors with WordPress itself - when I enable logging, nothing show. I've also redeployed it vis capistrano, so it has the latest working code. Where are the error logs for MariaDB saved?

[Foxaii]

See if you can log into the dashboard. If you can, deselect and reselect your theme.

[mAAdhaTTah]

I can't access that either (same white screen). I'm pretty sure the issue is in the server software, not WordPress.

[mAAdhaTTah]

If no one else has experienced this, I'm going to just destroy and re-provision the droplet. I have everything backed up, I was just hoping to avoid re-uploading all those pictures. Thanks for your help guys!

[mAAdhaTTah]

Errr, so that didn't work. Still getting a white screen.

FWIW, if I load up the Vagrant box and update all the software via apt-get, I get the same issue. Is this reproducible on your end?

[swalkinshaw]

@mAAdhaTTah figured out what happened.

Previously Nginx included fastcgi_param SCRIPT_FILENAME $request_filename; in fastcgi_params which we include in wordpress.conf.

Upgrade Nginx removes that lines and also adds a new fastcgi.conf file. So the solution is either to re-add that line to fastcgi_params or include fastcgi.conf instead.

I'm going to choose one of these and fix this and bump the version/update base Vagrant box.

[swalkinshaw]

Fixed by 02879c2

[swalkinshaw]

Box has been upgraded as well: https://vagrantcloud.com/roots/boxes/bedrock/versions/3

[mAAdhaTTah]

Great! Thanks for your help.