Lemmy.ca Support / Questions

539 readers

1 users here now

This community is for support requests specific to lemmy.ca.

If you need to contact an admin privately, please message @[email protected].

If you are a technical user and you have questions or need support with the Lemmy software itself, please visit [email protected].

founded 4 years ago

MODERATORS

[email protected]

Time outs (lemmy.ca)

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

21 comments fedilink hide all child comments

Ever since things came back up after the Jan 5th outage, I've started to encounter regular timeouts. I will scroll past a couple dozen number posts and then it will stop as of there are no more. Within a few seconds, the application produces a time out error.

I use Boost for Lemmy as my client, but I'm not convinced that the issue is the app since switching my instance allows me to continue scrolling without a problem. And to be clear, prior to January 5th, I've never experienced a timeout in the app.

I'm curious if I'm the only one experiencing timeouts on Lemmy.ca. If so, then I'm curious if the admins are aware of any issue.

[10 Feb 2025 Update: After Lemmy.ca was updated to 0.19.9, cloudflare account changed, and their hardware infrastructure replaced... everything has started functioning normally again. I can't say what the cause was yet, but the WebUI and any connected app is scrolling through feeds without any timeouts now. 💯]

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 1 points 2 months ago (1 children)

Is this gone now we're on the new server?

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

With the server migration and the back end update, I really had high hopes. Haha. But alas... The All feed times out when I try to go to the next page with Boost. I went to the web UI and hit next it sure enough times out as well.

The secondary account I created doesn't have the problem at all.

I appreciate you checking into the logs before. I'm still really curious about the cause, but it seems like I'm the only one struggling with this. I don't really want to waste more of your time.

I will probably do a little more troubleshooting out of curiosity, but I don't have high confidence that it's going to be rectified.