I will be starting the upgrade for all Mastodon servers on Masto.host to v3.2.1
There should be less than 30 seconds of downtime during the process.
You can see the changelog here: https://github.com/tootsuite/mastodon/releases/tag/v3.2.1
Any issues or questions please let me know.
The upgrade is installed. All Mastodon servers on Masto.host are now running v3.2.1
Any issues please let me know. Thanks 🐘
@mastohost curious to know if you have any problems - since I upgraded my instance, federation with relays has been broken (mastodon.web returning 401 unauth'd to relays' posts) for unknown reasons... :-(
@tim Everything is working fine on my end. What version were you before the upgrade? Did you jump multiple versions?
@mastohost no, 3.2.0 to 3.2.1. Seems maybe related to certificates/auth keys, might be specific to the relay software (federating between mastodon instances works fine, or I'd not see your post :-)). As ever, when it works it works and when it doesn't you're on your own; hopefully I'll have time to dig in deeper at the weekend...
@tim hummm... what steps did you perform during the upgrade?
@mastohost I changed the image tav from v3.2.0 to v3.2.1 and redeployed the Docker container 😁. Nothing else indicated in the readmes/changelog :(.
@mastohost Kubernetes, so the equivalent using helm. And yes, tootsuite/mastodon.
Rolling back doesn't fix the problem (it just changes it to http/202 errors instead of 401), so it persistently breaks something. Makes me suspect that it's borked wherever it stores the key/certificate it uses to validate the relay's key; whether that's redis or postgres I don't know, but that's where I'll start digging at the weekend...
I do appreciate your taking the time, by the way! Thanks.
@mastohost: After doing a little more digging, I strongly suspect this change is to blame - https://github.com/tootsuite/mastodon/pull/14556
- which somewhat breezily breaks compatibility with other suitably 'old' Fediverse software. Which doesn't seem a super smart thing to do in a point release, at least not the way I understand SemVer...
More interesting to me now is why downgrading back to 3.2.0 didn't seem to fix things 😐
@mastohost: OK, to answer my own question downgrading did fix the problem after deleting and adding the relays again.
So, short version - don't upgrade to 3.2.1 if you value federating with "old" Fediverse instances, 'cos the new changes to signature validation break it.
@tim so, docker-compose down and docker-compose up -d? you are using tootsuite from hub.docker, right?