Voyager

6970 readers

45 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

[email protected]

I can no longer view feddit.uk in the latest app update (feddit.uk)

submitted 2 days ago* (last edited 2 days ago) by [email protected] to c/[email protected]

4 comments fedilink hide all child comments

Since I updated to the latest version of the app - to fix an issue I was having with another error, I can no longer view feddit.uk instance. I initially thought feddit.uk was down and went to view in browser. If I click from an external browser URL and point it to Voyager to control opening it, I get an unknown URL error after the attempt at loading has timed out. (See attached video). I can view other instances e.g. lemmy.ml or lemmy.world but not this one. I downloaded Jerboa just to check but haven't used it yet.

Edited to add video

EDITED - Thanks for the replies. It must be my devices so. I thought it might be my DNS settings which I have set to Adguard DNS, but I disabled that and it made no difference. I will do a fresh install of it tomorrow and see if that helps.

top 4 comments

sorted by: hot top controversial new old

[–] [email protected] 2 points 2 days ago* (last edited 2 days ago)

I did a fresh install today. No luck. I can't even pick feddit.uk without an error (Attached image). Version 2.37.2 It's a shame, I like voyager, but I've got a couple of errors. So for now I've downloaded another app and I'm using that instead. Will try again after the next update. 🤞

[–] [email protected] 7 points 2 days ago

Video isn't working, but feddit.uk is loading fine on my device.

[–] [email protected] 4 points 2 days ago* (last edited 2 days ago) (1 children)

Works for me. Running Voyager on iOS. (version 2.37.2)

[–] [email protected] 3 points 1 day ago

Seems it's the same version on Android that has broken access to some instances. There's an update on the GitHub page that fixes it. 2.38.0