this post was submitted on 02 Jul 2026
1 points (66.7% liked)

LemmyToday

312 readers
4 users here now

If you experience issues or problems with this instance (lemmy.today), this is the place to discuss them. Or if you just want to ask questions about how something works. Anything related to the instance or lemmy itself.

founded 2 years ago
MODERATORS
 

Not sure what's going on, but for at least today and yesterday, I've seen a fairly high rate of server errors when attempting to load a number of different sorts of pages. I've seen this happen with attempting to view a post (including on communities that are not locally hosted), and attempting to view user pages.

As far as I can tell, if one keeps reloading, one eventually gets through, if you're hitting this. No idea as to cause


all I see is:

Error!

There was an error on the server. Try refreshing your browser. If that doesn't work, come back at a later time. If the problem persists, you can seek help in the Lemmy support community or Lemmy Matrix room.

Sorry I can't provide any additional information, but I can't think of much other information.

An example page:

https://lemmy.today/post/55800972

This successfully showed up on, I believe, my sixth reload. The seventh reload was an error again (so it's not a "it works once and then keeps working" problem for a given page). I've seen it on various networks on my end, so I'm pretty sure that I'm not a factor.

https://lestat.org/ doesn't show errors, so whatever it is, it's not tripping their error detector.

you are viewing a single comment's thread
view the rest of the comments
[–] tal@lemmy.today 1 points 19 hours ago (1 children)

I was still seeing it yesterday


as well as a brief period of it returning some 500 HTTP error code


but not, so far, today. I'll follow up if it does show up.

[–] mrmanager@lemmy.today 1 points 19 hours ago (1 children)

I was fixing one thing today with old.lemmy.today but it shouldnt affect lemmy.today.

old.lemmy.today was putting all visitors under the same IP so lemmy was rate limiting everyone randomly who used old.lemmy.today. But that is fixed today. It doesnt sound like the same thing as your problem though, unless lemmy.today was also overloaded because of its rate limiting old.lemmy.today.

We will see if you get the same thing today then!

[–] tal@lemmy.today 2 points 19 hours ago* (last edited 9 hours ago)

Gotcha, thanks!

EDIT: Hasn't emerged today tht I've seen. Dunno if it was another DDoS or load from scrapers or something else, but it hasn't appeared to show up today, at least that I can see.