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.
Hey @capb994,
The “413 Request Entity Too Large” error message is coming from your Nginx server. It is not from DigitalOcean or your Express.js server. This error is usually thrown when the size of the HTTP request (i.e., the data being sent in the request body) exceeds the client_max_body_size directive in the Nginx configuration.
To answer your other question, no DigitalOcean wouldn’t be restricting or limiting such uploads.
Location of the Directive: If client_max_body_size is defined in different places in your Nginx configuration, the one defined in the most specific context will be used. For instance, if it’s defined in the http context and also in a server context, the server context will be used. Make sure you’re defining it in the right place.
The Other Server: If the request is being proxied to another server, it’s possible that the error is coming from that server. You should check the configuration of the other server to make sure it’s also able to handle large request bodies.