Why am I receiving 520 status codes from my app?

Validated on 20 Mar 2025 • Last edited on 3 Apr 2025

A 520 status code means your app returned an invalid or empty response. This can happen when an app crashes while trying to receive an upload or trying to return a response larger than it has been configured to manage.

For example, Next.js apps can return a 520 status code when the app crashes while trying to a return a response size larger than 4 MB or when receiving a file upload larger than 1 MB. The crash usually occurs before any logs can be generated, making it difficult to diagnose.

Before deploying your app to production, we recommend checking your framework’s resource management settings such as memory allocation, request timeouts, maximum payload sizes, and maximum response size, and also error handling for configurations that don’t meet your app’s needs.

Why am I getting an error when trying to forward DigitalOcean Functions to Managed OpenSearch?

Functions does not support forwarding to Managed OpenSearch.

My container-based app fails to deploy without logs or error codes.

Troubleshoot by making sure the Dockerfile and its commands build on Linux AMD64 and other steps.

How do I generate my app's SSL certificate?

App Platform automatically generates and issues the SSL certificate during the configuration.

We can't find any results for your search.

Try using different keywords or simplifying your search terms.