Lemmy.ca Support / Questions

499 readers

2 users here now

Support / Questions specific to lemmy.ca.

For support / questions related to the lemmy software itself, go to [email protected]

founded 4 years ago

MODERATORS

[email protected]

Time outs (lemmy.ca)

submitted 2 days ago by [email protected] to c/[email protected]

13 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.

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

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

That is odd, I'm on Boost as well and haven't noticed this. I'll pass it along to the team and poke around!

The outage was a hardware issue and I don't think we changed any site configuration since then. At least on our end, having the hardware replaced seemed to have fixed the occasional hiccups we were seeing.

In the meantime, could you try clearing the app's cache? Boost lets you make a backup of the settings, which can help give peace of mind before doing resets.

If anyone else has this problem, please do share!

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

Ugh. Decided to select the All feed and scroll away. And... it timed out after one "page"** worth of posts...

And boy did it stop on the worst post ever... (Note the time out error)

** I'm defining "page" as the number of posts displayed until you have to click the "next" on the standard web UI.

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

Thanks for the response. I have one inkling of an idea that might be a cause, but it really should affect the whole app rather than a single instance.

I've cleared the cache already but perhaps I might try backing up and clearing all data. Gonna keep monitoring for now.