Voyager

And I'm back. Whew, that was a rough upgrade. I had to do some manual PostgreSQL surgery to get it past 0.19.3 - there were two versions of the hot_rank function so the migration script was failing.

Then I noticed the logs were full of pictrs spitting out "Read corrupted data..." and crash looping, and I spent a couple of hours trying to get it to do anything. I finally had to give up and nuke it, so I guess the few images I've posted over the years are 404s now.

I started to get discouraged and I was going to just decommission the server, but I'll try to learn my lesson and keep a closer eye on it so I can catch future problems before it's too late.

hi there
same problem
can't connect with using 2.37.2 version
And
you can try back to previous version
like 2.36.0 ( ͡° ͜ʖ ͡°)

Ah, thanks for letting me know. I just checked and it's because you're running lemmy v0.19.3. That's pretty old; I would recommend upgrading.

That being said, Voyager should have more helpful error messages for unsupported versions, and also should still support 0.19.3 until the next major release, so I'll push a fix.

I've been noticing the same, on and off. At first I thought it was my instance, but it's fine on its own and through other UIs.

Aside from your thread, all else I could find was this issue, which is from May, long before I started noticing this, so not sure it's the same problem

Voyager pulls /.well-known/nodeinfo now, if you don’t proxy that to your backend (I didn’t), it will fail.