AutoGPT v0.11.0 Adjusts Proxy Trust and API Size Limits; Self-Hosted Deployments Must Update Settings

AutoGPT released Platform v0.11.0 on November 4, marking several deployment behavior changes as breaking updates. Among them, reverse proxy trust settings and API request size limits directly affect the entry points used by existing proxy workflows: the former changes which IP is used for per-visitor rate limiting, while the latter may cause large inputs that were previously accepted to receive an HTTP 413 response. Official release notes

In multi-proxy environments, X-Forwarded-For often contains multiple addresses. The new version requires administrators to list trusted proxy IPs or CIDR ranges using TRUSTED_PROXIES. If it is not set, the system no longer takes the leftmost address in the header directly, and workflows that apply per-visitor limits will not have access to the user’s IP. If the list contains an invalid address or range, the frontend will fail to start. Teams deploying behind a CDN, load balancer, and reverse proxy should therefore confirm the actual proxy chain and configuration format first. Change details

Another change is MAX_REQUEST_BODY_MB: by default, standard API routes reject request bodies larger than 10 MiB, while upload routes and webhook endpoints are excluded from this rule. If an application embeds large files directly in requests, teams will need to raise the limit or configure media storage after upgrading. Engineers should validate standard inputs, file uploads, and webhooks separately, rather than assuming the same limit applies to every route. API limit details

The official self-hosting documentation describes two deployment options: a single container and Docker Compose. It positions the single-container option for local and small-scale installations. The documentation also cautions that existing environment files do not automatically incorporate all newly added variables, so upgraders still need to compare them against the default settings. This makes configuration differences a practical focus for checks during this update. Self-hosting documentation

The impacts above are summarized from the official release notes and have not been independently tested in a deployment for this article. Teams should next verify IP determination and rate-limiting behavior behind their proxies, along with error handling for large requests. The release itself does not establish that any particular deployment’s proxy chain and file workflows are compatible.