The self-hosted upgrade is stuck
A jump from Ghost 3 or 4 to Ghost 5 that stalled mid migration, usually tangled up with an unsupported Node version or a MySQL that no longer matches what Ghost expects.
Upgraded on a staged copy first
Working with Ghost?
Ghost is lovely until you self-host it and the ghost-cli command walks you into nginx, systemd and a Node version you cannot change. We get the site publishing again and the member subscriptions billing cleanly.
What it is
Ghost is an open-source publishing platform started in 2013 by John O'Nolan and Hannah Wolfe after a Kickstarter campaign to build a cleaner alternative to WordPress. It is written in Node.js and uses MySQL in production, with a focused editor aimed at writers and publishers rather than general web design.
Ghost 4 arrived in 2021 and added Members and Stripe-based paid subscriptions, which turned the platform into a direct competitor to Substack. You can run it yourself for free under the MIT licence, or pay for Ghost(Pro) managed hosting. Themes are written in Handlebars, sign-ups happen through the Portal widget, and both a Content API and an Admin API are available for integrations.
The honest version
No technology is all upside. This is where Ghost earns its place and where it tends to cause trouble.
Sound familiar?
The Ghost problems that bring people to us, and what you have once each one is fixed.
A jump from Ghost 3 or 4 to Ghost 5 that stalled mid migration, usually tangled up with an unsupported Node version or a MySQL that no longer matches what Ghost expects.
Upgraded on a staged copy first
Stripe is taking the money but Ghost is not marking the member as paid, because the webhook endpoint or the connected Stripe account is no longer wired up correctly.
Members billing cleanly again
A cold sending domain, missing SPF and DKIM records, or a list that has collected enough bad addresses for Mailgun to pause the account.
Deliverability restored and monitored
A quick install that left SQLite in place where Ghost expects MySQL in production, which breaks backups, breaks migrations and eventually breaks under load.
Moved to MySQL with data intact
Another web server already holds port 80, or the server was set up in a way the installer did not expect, so the automation bails out halfway through.
Installed and serving traffic
A rotated Content or Admin API key, or a site URL change that invalidated the signed token the external app was using.
Integration reconnected and tested
Media files not copied across, authors mapped to the wrong accounts, and old /category/ URLs returning 404 to Google.
Content and redirects complete
A renewal hook that ghost-cli set up years ago and nobody has checked since, so the site goes to a browser warning on a quiet weekend.
Renewals verified end to end
What we do
Call us for one upgrade, or hand us the whole publication.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
Yes. We stand up a copy of your site at the current version, step it through the required intermediate releases, line up the Node and MySQL versions Ghost 5 expects, and only cut over production once the copy is fully working.
It depends on how your member count is growing and how much server work you want to own. Ghost(Pro) removes the ops burden but the per-member pricing climbs quickly, while self-hosting is cheaper at scale and strictly more work to run.
Yes. We bring across posts, authors and media, map every old URL to its new one with proper 301 redirects, preserve canonical tags and feed URLs, and watch Search Console for weeks after the switch.
Usually the sending domain has no SPF, DKIM or DMARC records set up, or Mailgun was never warmed up before a large send. Sometimes the list has old addresses pushing the bounce rate past what Mailgun will tolerate.
Yes. We work in Handlebars against a starter theme such as Source or Casper, keep the editor and Portal experiences intact, and ship the result as a theme file you own.
Estimates are free. Tell us what is broken or what you want to build and you get a price before any work starts.
Free estimate
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: