sandbox_defaults.outbound_proxy in global configuration for a shared default. Administrators can enforce or clear it through managed configuration, which takes precedence over per-sandbox CLI and SDK options.
Supported proxies
You can configure only one proxy for a sandbox. A SOCKS4 user ID identifies the caller; it is not a password.
Configure a proxy
IP:port. The msb run and msb create commands accept --proxy http://IP:port, socks4://IP:port, or socks5://IP:port. Proxy URIs reject user information, paths, query parameters, and fragments; SOCKS authentication uses separate CLI flags.
HTTP CONNECT
HTTP CONNECT opens a TCP tunnel through an HTTP proxy. It supports optional HTTP Basic authentication and TCP only; UDP is unsupported. microsandbox resolves and checks the destination using its normal DNS and egress policy before sending the destination IP and port in the CONNECT request. The proxy address itself must be an IP address with a port. The selectedmsb runtime must support HTTP CONNECT. When using an older runtime, the SDK requests an upgrade before creating or replacing a sandbox.
SOCKS4 user ID
Add an optional user ID through an SDK or--socks4-user-id in the CLI.
SOCKS5 credentials
SOCKS5 supports optional username/password authentication. Passwords are loaded from a host environment variable rather than placed directly in configuration.- Password source: Set the password in a host environment variable, the only supported source. Configuration stores only the variable name, such as
SOCKS5_PASSWORD, never the password. - When changes apply: The password is read when the sandbox starts. Restart the sandbox after changing it.
- Requirements: The username and password must each contain 1–255 bytes. Startup fails if the password variable is missing, empty, or invalid.
HTTP CONNECT credentials
HTTP CONNECT supports optional HTTP Basic authentication. Passwords are loaded from a host environment variable rather than placed directly in configuration.- Password source: Set the password in a host environment variable, the only supported source. Configuration stores only the variable name, such as
HTTP_CONNECT_PASSWORD, never the password. - When changes apply: The password is read when the sandbox starts. Restart the sandbox after changing it.
- Username: RFC 7617 permits an empty username for token-only authentication. A non-empty username must not contain
:or control characters. - Password: The resolved password must not be empty.
- 407 responses: A proxy that requires authentication is refused instead of retried without credentials. The error distinguishes missing credentials from rejected credentials.
- Runtime support: The selected
msbruntime must advertise the HTTP CONNECT authentication capability. An older runtime fails the launch with an upgrade-required error instead of silently connecting unauthenticated.
Behavior and limits
- Network policy is evaluated against the sandbox’s actual destination before the proxy connection is opened.
- HTTP CONNECT and SOCKS4 support TCP only. Non-DNS UDP is blocked while either is configured; SOCKS4 also cannot reach IPv6 destinations.
- SOCKS5 uses
CONNECTfor TCP andUDP ASSOCIATEfor non-DNS UDP. - DNS uses microsandbox’s DNS forwarder instead of the configured proxy. This includes plain DNS, DNS-over-TCP, and DNS-over-TLS.
- Connections to
host.microsandbox.internalbypass the proxy and continue to target the microsandbox host. - Each TCP connection opens its own proxy connection and handshake. Each UDP flow opens its own SOCKS5 control connection and UDP association.
- HTTP CONNECT authentication uses HTTP Basic credentials on the CONNECT request; see HTTP CONNECT credentials for the 407 behavior.
- TLS interception and secret injection continue to work as configured.