Report this

What is the reason for this report?

Nginx 502 Bad Gateway S3 Upload

Posted on November 27, 2016

I am running a Phoenix (Elixir) application and using arc and ex_aws to upload images to S3. Arc will stream the upload to S3. However, a PATCH with the uploaded base64 image immediately returns a 502.

So one theory is nginx is getting confused b/c it is streaming the upload but receives a response early and nginx thinks something went wrong. The reason why I believe Nginx is causing this is b/c uploading locally on my Mac works perfectly.

Here is the nginx configuration:

https://dustinfarris.gitbooks.io/phoenix-continuous-deployment/content/phoenix_server/nginx.html

Any thoughts would be greatly appreciated!



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.

You may need to adjust the proxy buffer size to prevent 502s when uploading via the nginx proxy. This page covers some solutions to this issue. Having something like the following in your configuration should help:

# define buffers, necessary for proper communication to prevent 502s
proxy_buffer_size 128k;
proxy_buffers 4 256k;
proxy_busy_buffers_size 256k;

The developer cloud

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

Get started for free

Sign up and get $200 in credit for your first 60 days with DigitalOcean.*

*This promotional offer applies to new accounts only.