Error contacting the Parsoid/RESTBase server (HTTP 404) is interesting, I wonder what request specifically is triggering this

a client request body is buffered to a temporary file might be fixable with some nginx tweaks and or upping the memory, i woudlnt imagine this should result in a 404 landing back with a user request though

Is delaying request some part of your rate limit setup?

I wonder if there might be some way of tweaking your rate limiting to affect users less. perhaps the bot spam doesnt coe with a Referer header? but most user traffic does? (depends on how their bots are working)

In T392907#10779232, @Addshore wrote:

Error contacting the Parsoid/RESTBase server (HTTP 404) is interesting, I wonder what request specifically is triggering this

Yeah, I don't actually see a 404 in our logs and I'm not certain how this error appears to the user other than the report from telegram.

a client request body is buffered to a temporary file might be fixable with some nginx tweaks and or upping the memory, i woudlnt imagine this should result in a 404 landing back with a user request though

yeah, this is probably because the NGINX is already creaking a bit from the traffic at the exact time these requests came in.

Is delaying request some part of your rate limit setup?

Yes! Using the built in nginx stuff

I wonder if there might be some way of tweaking your rate limiting to affect users less. perhaps the bot spam doesnt coe with a Referer header? but most user traffic does? (depends on how their bots are working)

Sure, in fact I'm certain there are better ways I'm just not sure where they are. In general "bot management" seems to have become a huge topic recently and many people are playing the cat and mouse game of detect a bot-vs-pretend not to be a bot (some random source for this being a general thing: https://www.imperva.com/resources/resource-library/reports/2025-bad-bot-report/).

For now we're going to just observe if we get additional reports of this or if it's just a transient issue relating to incoming traffic

I have observed that VisualEditor loads on a new page, allowing me to edit it. However, when I attempt to save it, this error appears. When opening an existing page in VE, the error comes immediately. If I try to move to wikicode from VE on a new page, the error message also appears.

Moving to incoming to discuss with @Tarrow at next backlog check

@Juandev Hello,
We couldn't reproduce this on a test Wikibase, so I requested an account on ugly architecture. Could you please approve it, so we could try there?
Thanks

Couldn't reproduce it directly on uglyarchitecture either.
@Juandev is it still reproduced for you? If so, could you please share screenshots?