Voyager

6941 readers

60 users here now

The official lemmy community for Voyager, an open source, mobile-first client for lemmy.

Rules

Be nice.
lemmy.world instance policy

Sponsor development! 👇

💙

founded 2 years ago

MODERATORS

aeharding@lemmy.world

aeharding@vger.social

Why did Voyager break for my server? (lemmy.masto.community)

submitted 2 days ago by masto@lemmy.masto.community to c/voyagerapp@lemmy.world

5 comments fedilink hide all child comments

I have been running a personal lemmy server for a long time and using Voyager (web app). The other day I updated as I have done dozens of times before, and it wouldn’t load any posts. I tried logging out and clearing my cache, but when I try to log in to lemmy.masto.community, it just says there was a problem connecting.

The server is obviously up and working or I wouldn’t be able to post this. And logged out, I seem to be able to browse public servers with Voyager. It has just suddenly become incompatible with… something? This is a managed service on Elestio, so it’s maintained automatically.

I figured if I waited a few days it would sort itself out since I can’t be the only one. But I don’t see any posts about this so now I’m wondering if I’m the only one. Any ideas? Thanks!

top 5 comments

sorted by: hot top controversial new old

[–] Xyii@fasheng.ing 1 points 16 hours ago* (last edited 16 hours ago)

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 ( ͡° ͜ʖ ͡°)

[–] aeharding@vger.social 23 points 2 days ago (1 children)

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.

[–] masto@lemmy.masto.community 8 points 2 days ago

Thanks very much!

I didn't realize it was outdated; I get emails from Elestio regularly (including just this week) that it was automatically updated to the latest version. Apparently I forgot (it's slowly coming back to me now) that at some point something broke on an upgrade and I must have pinned the version back in early 2024.

I just tried to move it forward and unfortunately, anything after that version breaks with a failing schema migration (maybe the same problem I had back then). I restored a backup for now and I'll figure out how to fix it over the weekend.

I appreciate the assistance and info.

[–] jutty@blendit.bsd.cafe 6 points 2 days ago

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

[–] farcaller@fstab.sh 2 points 2 days ago

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