DigitalOcean Kubernetes: new control plane is faster and free, enable HA for 99.95% uptime SLA

Question

Nginx 502 Bad Gateway S3 Upload

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!

Submit an answer

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!

Sign In or Sign Up to Answer

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.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

Sign up now

Ryan Quinn • December 15, 2016

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;

Try DigitalOcean for free

Click below to sign up and get $100 of credit to try our products over 60 days!

Sign up