Meta (lemm.ee)

3592 readers

1 users here now

lemm.ee Meta

This is a community for discussion about this particular Lemmy instance.

News and updates about lemm.ee will be posted here, so if that's something that interests you, make sure to subscribe!

Rules:

Support requests belong in !support
Only posts about topics directly related to lemm.ee are allowed
If you don't have anything constructive to add, then do not post/comment here. Low effort memes, trolling, etc is not allowed.
If you are from another instance, you may participate in discussions, but remain respectful. Realize that your comments will inevitably be associated with your instance by many lemm.ee users.

If you're a Discord user, you can also join our Discord server: https://discord.gg/XM9nZwUn9K

Discord is only a back-up channel, !meta@lemm.ee will always be the main place for lemm.ee communications.

If you need help with anything, please post in !support instead.

founded 1 year ago

MODERATORS

sunaurus@lemm.ee

Cannot load additional pages in Jerboa (lemm.ee)

submitted 1 week ago* (last edited 1 week ago) by JakenVeina@lemm.ee to c/meta@lemm.ee

9 comments fedilink hide all child comments

Started getting an error "Posts failed loading, retry" whenever Jerboa attempts to load more posts from the "All" feed. This does not seem to happen when viewing specific community feeds. Refreshing the entire feed still works just fine, and produces new posts. I swapped to a couple other instances, such as lemmy.world, and did not get the same behavior. This just started yesterday, 2024-11-17.

I'd upload an image, but image uploads are also broken, have been for a few days.

UPDATE: Seems to be fixed, at the moment.

top 9 comments

sorted by: hot top controversial new old

[–] Thymos@lemm.ee 2 points 5 days ago* (last edited 3 days ago)

I have the same issue, been having it for a few more days and still not resolved today. The subscribed feed loads fine though.

Edit: problem is fixed now.

[–] Galaxy@lemm.ee 3 points 6 days ago

I also am having this same issue on boost

[–] Encode1307@lemm.ee 4 points 6 days ago

I'm still having this problem on boost

[–] HuntressHimbo@lemm.ee 6 points 1 week ago* (last edited 5 days ago) (1 children)

I second this. I am having the same issue in Jerboa, but also through the web interface. First page loads just fine, but no additional pages will load

EDIT: Looks like this has been fixed for me

[–] JakenVeina@lemm.ee 2 points 1 week ago (1 children)

Interesting. The web UI doesn't give me that issue. It is HORRENDOUSLY slow, though. It periodically freezes for as much as minutes at a time.

[–] scsi@lemm.ee 3 points 6 days ago* (last edited 6 days ago) (1 children)

"How long are you willing to wait for the page load" seems to be the intersection; I have the same problems (Jerboa and webUI) and frequently just give up waiting on the webUI. My guess is that the internal Jerboa timeout-wait triggers quicker than a human waiting, so they're one in the same problem.

I received a 504 gateway error this morning trying to load lemm.ee front page too, the status.lemm.ee page says everything is OK but... well, shenanigans. Strange things afoot at the Circle-K.

Edit (testing): my reply below reverse-federated back almost instantly as well. Federation gets an A+, gold star.

[–] scsi@lemmy.world 1 points 6 days ago

(testing) Federation seems on track, my reply showed up almost instantly on lemmy.world

[–] SHOW_ME_YOUR_ASSHOLE@lemm.ee 5 points 1 week ago

I am having a similar issue but I'm using the Voyager app.

[–] InquisitiveApathy@lemm.ee 4 points 1 week ago* (last edited 6 days ago)

Just chiming in to say I've been having the same issue. Pages beyond the first (so maybe about 10 posts or so at a time) will not load and get stuck with a red "pages failed loading" error at the bottom of the screen in Jerboa. This behavior started over the weekend. All other navigation seems fine, I can go to a community and sort by any of filters but only the first page of posts will be visible. I've got about a half dozen different accounts on different instances and the issue only happens when logged into this instance at this time.

Edit: Unlike OP I never stopped having the issue. It's still present post maintenance and upgrade.