tomspark wrote:
Nothing wrong on your side — if that button says "Export Failed", that's on us. You're the first to report it, so thanks for flagging. I've logged it and we're digging into what's tripping it up right now. Your config itself is safe and untouched — the export just isn't producing the file it should. I'll follow up here as soon as there's a fix or a workaround for you.
tomspark wrote:
Thanks for confirming — you're the second person to hit this, so it's definitely a bug on our end, nothing wrong with your setup. Your config is safe; the export just isn't producing the file it should. It's already logged and being worked on. I'll post here the moment a fix ships so you both know when to update.
Chris wrote:
Owed you both this update, and it is well overdue — sorry it sat. The export fix has shipped: it went out in v1.6.334 on 12 July. Worth knowing why it took two attempts. A fix genuinely did ship on 5 July, then vanished the same day: two separate releases were built under the same version number and the second overwrote the first in storage, taking the export fix with it. v1.6.334 re-landed it, and the release pipeline can no longer reuse a version number at all. Grab it with sudo sparkbox upgrade — that is the one that moves you to a new release, whereas update only refreshes app images. Then try Tools → Server Migration again. — Chris