Sorry actually do not know where that error comes from. If from n8n (so Node.js) or the reverse proxy. But considering that apparently n8n crashes even with 10k rows, as it probably runs out of memory, does increasing the request limit not really help anyway.