Pain point · Self-hosting & upgrades · Causes churn
Upgrade from 5.38 to 6.0 fails with a database column conversion error
5 source threads · first seen 2017-07 · last seen 2026-05
Summary
The server fails to start after the upgrade because a migration cannot convert a column to JSONB, leaving the instance down.
- Affects
- Debian self-hosters
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Migrate from 10.11.17 to 11.17.0 and observe a migration failure”
“After upgrading from an unknown version (something 10.x) to 10.6.1, I as a system admin cannot list the channels”
“After updating mattermost from 6.3.3 to 6.4.0, i got this failed migration error”
“Upgrading from Matermost 5.38 to 6.0 leads to mattermost failing to start”
“Mattermost not available after Upgrade to 4.0.0 via Browser and Mattermost Desktop”