For me it's because for whatever reason, Verizon has files.catbox.moe DNS blocked so any picture using that service to host fails to load when using phone data. Your problem might be something similar.
Sync for Lemmy
๐
Welcome to Sync for Lemmy!
Welcome to the official Sync for Lemmy community.
The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:
Community Rules
1- No advertising or spam.
All types of advertising and spam are restricted in this community.
Community Credits
Artwork and community banner by: @[email protected]
Nah, Australian provider and I'm on the home wifi almost all the time I'm on here. Thanks for the suggestion though.
I also get this periodically on WiFi and data.
@boogetyboo there's still a good chance you're using your Internet Service Provider's DNS.
Not only does this mean its super trivial for them to block things they don't want you to access, but this also means they can see (and they probably log) everything you do; no good for privacy or freely accessible info
Try switching to something like quad9, and reboot your devices after to make sure they've cleared their DNS cache
PS:
You can just add dns.quad9.net to Settings > Network > Private DNS on Android if you don't want the app.
Thanks for this. Have added to DNS settings and will see how I go.
I prefer dns.adguard.com so you get pretty decent dns-level adblock too
Yeah don't use your ISP's DNS
I frequently get this too
Do you have an example link?
This one loads for me.
Device information
Sync version: v24.03.26-14:56
Sync flavor: googlePlay
Ultra user: true
View type: Slides
Push enabled: false
Device: e3q
Model: samsung SM-S928U
Android: 14
I have no idea why, but I just tried it again and it loaded for me this time. But it wasn't loading and I got the exact message described in the original post at the time.
Kiwi here, no such issues with my Sync. Is there a particular community where you see these errors mainly (if so, can you link it here)?
Also, when you get those errors, it might be worth accessing that community directly using a local account - and if the images load fine, that would point to a federation issue with your server.