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.
Alright, @[email protected]. Here’s some more information.
General Findings
Findings by Server
Errors By Application Note the differences in how the error is presented. Sending timestamps and IP to @[email protected] via DM for the following:
simply renders empty after the timeout. this was page 2
I suspect something might be funky with your account, rather than the network / apps. The timeout message is a lie, you’re really getting 400 / 499 errors that seem to be related to this lemmy error message:
2025-01-20T17:30:03.366014Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: NotAModOrAdmin: NotAModOrAdmin 0: lemmy_api_common::utils::check_community_mod_of_any_or_admin_action at crates/api_common/src/utils.rs:102 1: lemmy_api::local_user::report_count::report_count
and:
2025-01-20T20:39:43.202677Z WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: CouldntFindPerson: Record not found 0: lemmy_apub::fetcher::resolve_actor_identifier at crates/apub/src/fetcher/mod.rs:22 1: lemmy_apub::api::read_person::read_person
I wonder if it could be a bug related to the unicode name you’ve got going on. Did you set that recently, or has it been like that since day 1?
I just restarted all of our docker containers, see if that helps? If not, try setting a normal name and confirm if that changes things?