Ancestors

Toot

Written by fmstrat on 2024-09-26 at 21:15

400 and 499 errors in NGINX logs

https://lemmy.nowsci.com/post/10663526

=> More informations about this toot | More toots from fmstrat@lemmy.nowsci.com

Descendants

Written by Andrew on 2024-09-28 at 21:46

Oh. I subscribed to this post because I hoped someone would be able to give an answer too.

It's been a day, so before I forget and on the basis that some answer is better than none at all, I'll have a crack:

400 Bad Request isn't much to worry about, it doesn't mean anything is malfunctioning and it can happen for a gazillion reasons. One is you've joined a new community and someone Likes a comment you don't have (particularly if it's nested in other comments you also don't have). Another is if someone Likes a post or comment by a user on an instance that you've defederated from (your instance is defed'd from lemmygrad and hexbear whereas lemmy.ml isn't)

As for 499, that seems to be a client issue, and that client mostly seems to be beehaw, who are stuck on an old Lemmy version and being increasingly wonky (in the other direction, they often reply in HTML rather than JSON and randomly decide that their communities' inboxes don't exist, so I wouldn't worry about stuff from them either)

=> More informations about this toot | More toots from andrew_s@piefed.social

Written by fmstrat on 2024-09-30 at 02:16

It ended up being an outbound connectivity issue due to firewall changes. Doh. The thing that confused me is Lemmy.ml was still making it through without an outbound response.

=> More informations about this toot | More toots from fmstrat@lemmy.nowsci.com

Proxy Information
Original URL
gemini://mastogem.picasoft.net/thread/113205924376474917
Status Code
Success (20)
Meta
text/gemini
Capsule Response Time
249.038229 milliseconds
Gemini-to-HTML Time
0.463358 milliseconds

This content has been proxied by September (ba2dc).