Table of Contents
Update 2022-06-02
As of this morning, as far as I can tell everything is more or less working again. There appear to be a few issues with media decoding in Matrix for things that were uploaded in the day or so prior to the failure, but other than that I'm not seeing any problems.
Thanks for your patience, everyone! Let me know if any issues crop up for you.
Update 2022-06-01
Synapse has been restored and updated to 1.59, the current available version. There seem to be a few bugs with some of the recent messages, but given the ridiculous wizardry I had to enact to put everything back together, I'd say it's a small price to pay.
I'll be starting the Mastodon restore shortly. It's a hefty DB so the process might take most of the night, but hopefully by morning everything will be back to normal.
Update 2022-05-31
My experiments on my test server have pointed to the “uninstall Mastodon → restore Matrix from backup → restore Mastodon” path as the way to go. I'm waiting for the Mastodon restore to complete on the test server before I commit to that path on Moonbeam, but with any luck we should be back in business by the end of the week with all rooms and chats restored.
This is obviously suboptimal, and carries with it some risk of data loss, so to be safe I'd recommend that anyone who is using Mastodon should back up their accounts ASAP. If the test server comes back good I'm liable to just go ahead with the restore on Moonbeam in the interest of getting things back up as expediently as possible, so don't wait!
ETA: The Mastodon restore on the test server was successful so I'm going to go ahead and revert everything starting tomorrow morning. God willing, everything will be up and running again by tomorrow evening.
Greetings, programs!
As you have probably noticed by now, the Matrix-Synapse server run by moonbeam.town is inaccessible. This is due to a failed upgrade and reversion that I am attempting to sort out. I don't have a timeline for getting it back online, and due to a quirk in how the management software (YUNoHost) operates, it might not be possible to completely restore at all.
The Issue
The issue, as best I can tell, is a conflict between Mastodon and Matrix-Synapse when the two are installed to point to the same domain. Originally I had resolved this by installing Matrix-Synapse first and then Mastodon, which worked without issue, but now that Mastodon is installed it has “locked” access to the moonbeam.town TLD, which breaks the Matrix-Synapse upgrade process. Likewise, since reverting involves re-installing the old copy of Matrix-Synapse, the reversion process is also broken.
Can't you install Matrix-Synapse to a different subdomain?
It's possible, and this might end up having to be the solution, but I'd like to avoid doing so, as this would result in our Matrix IDs being @user:matrix.moonbeam.town (for example) rather than the current, nicer @user:moonbeam.town. Since this was working previously, it should be possible to implement again, so I'd rather explore other options before conceding defeat in this way.
What about uninstalling Mastodon?
Some users have suggested uninstalling Mastodon, installing Matrix-Synapse, and then restoring Mastodon from backup. This is also a potential solution, but carries risk of data loss within Mastodon so is likewise better avoided.
Are we going to get our rooms back?
Unclear. The solution I'm working towards involves restoring everything as it was. I've been keeping regular backups of all the data but those backups may or may not be usable given the bug in this process.
So what's the upshot?
Right now I'm trying to get assistance from the YUNoHost community in restoring everything. Best case, everything goes back to the way it was with an updated Matrix-Synapse. Other potential outcomes are:
- Matrix-Synapse is restored but we have to re-create all rooms and chats
- Matrix-Synapse is restored but on a subdomain
- Matrix-Synapse is restored but Mastodon's data is lost
I'll keep working this as I'm able, and I'll post updates here as they come up. I apologize to everyone for the inconvenience, and appreciate your patience as I work to resolve this.