@deuts@deuts.one

February 14, 2025
13:32

My #GoToSocial instance is now online. Pulled the image 0.18.0-rc2 and now everything seems back to normal:

services:
  gotosocial:
    image: superseriousbusiness/gotosocial:0.18.0-rc2

Here’s the Github issues that explained what happened: github.com/∞

I now got the status back up notification from #UptimeRobot:

Monitor is UP: Deuts One ( deuts.one/∞ ). It was down for 31 hours and 14 minutes.

What did we learn from this experience?

  1. Exclude GoToSocial in #Watchtower automatic updates.
  2. Stick to explicit version number in your compose.yml file.
  3. Time to re-think self-hosting your own Fediverse instance.
01JM1F3RHDNHSX7FYHS4JWT86K