The deploy wasn't the problem. Rolling back proved it — and restoring the database made things worse.
When production goes down right after a deployment, rolling back feels like the safest move. Put back what worked, get the sites up, investigate later. Most of the time that's right. This time it wasn't, and the logs showed why.
What happened
I deployed an update to six websites running on Servd , all powered by a single Craft CMS installation. The changes had been tested and approved on staging.
A few minutes after the deploy, the sites started returning errors and timing out.
My first thought was to roll back. I expected it to take a few minutes: get the sites running again, then find out what went wrong.…