Agent-sandbox vendor E2B retires self-hosted reverse-proxy service, repairs a broken SSL trust store in template builds; changelog names no insurance or indemnity terms

E2B, an infrastructure provider that runs sandboxed environments where AI agents execute code, said in an August 10 changelog entry that it retired a network component used on self-hosted deployments and fixed a certificate-handling defect. "This week retires the deprecated reverse-proxy service on self-hosted clusters, repairs SSL trust stores baked into templates, and unblocks Python SDK installs alongside newer wcmatch," the company said.

On the proxy retirement, E2B said the change requires action from some self-hosted operators: "Self-hosted deployments no longer build or ship the reverse-proxy service. DOCKER_REVERSE_PROXY_VERSION is removed from both .env.aws.template and .env.gcp.template , and a new DOCKER_REVERSE_PROXY_ENABLED toggle (default on) controls whether the AWS ECR repository is created and whether the GCP deployment runs. Clusters without a prebuilt docker-reverse-proxy:latest image must set the toggle to false."

The company also disclosed a defect in how sandbox templates were built. "Template builds that install SSL-related packages such as ca-certificates or openjdk no longer leave the finalized template with a half-configured package or a silently broken Java trust store. Directory paths under /etc/ssl/certs claimed by installed packages are restored before the certificate bundle is packed. Existing broken templates need a rebuild," E2B said. A silently broken trust store in a sandbox template is a runtime-integrity issue: a template that fails to validate certificates correctly could accept connections it should reject, without an operator being alerted, until the affected templates are rebuilt.

Separately, E2B said its Python SDK was updated for compatibility: "The Python SDK 2.37.1 relaxes its wcmatch requirement to >=10.1,<12 , so pip install e2b 'deepagents>=0.7.0' and other combinations that pull in wcmatch 11 resolve without a conflict."

The changelog entry does not address audit-trail, compliance-certification or outcome-based-payment terms, and names no insurance carrier, coverage limit, customer indemnity or liability cap, according to AI Dispatch's review of the entry.