Scale up as you grow — whether you're running one virtual machine or ten thousand.

From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.

This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
Hi @dgiulev,
When experiencing the mentioned issue, you most probably have something very similar in your Nginx Configuration file :
server {
listen 80;
server_name host;
location / {
proxy_pass http://upstream;
...
}
}
To resolve this issue, we need to increase the proxy buffers that Nginx uses.
Before Nginx sends a response back to your visitor, it will buffer the request it had to make from its upstream. However, there are limited buffers available to buffer such a response.
To resolve this issue, you’ll need to add proxy_buffer_size configurations to your location block.
Your location block for proxy_pass should look something like this
location / {
proxy_pass http://upstream;
...
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;
}
The above should help you fix the error you are experiencing
Regards, KDSys