TLS-inspecting proxies
Enterprises with strict egress monitoring requirements can route all bot container traffic through corporate forward inspection proxies, ensuring full compliance with DLP and firewall policies.
Corporate forward proxy routing
Configure proxy parameters at the organization level so every container automatically inherits standard environment variables (HTTP_PROXY, HTTPS_PROXY, and NO_PROXY).
# Injected automatically into all sandboxes
export HTTP_PROXY="http://proxy.internal.corp:8080"
export HTTPS_PROXY="http://proxy.internal.corp:8080"
export NO_PROXY="localhost,127.0.0.1,*.internal.corp,10.0.0.0/8"Installing custom CA certificates
When forward proxies decrypt TLS connections, client applications must trust the proxy’s root certificate. Plannix ensures every runtime environment (Linux system CA, Java Keystore, Python Certifi, Node.js, and OpenSSL) trusts your uploaded bundle.
Data Loss Prevention (DLP) filtering
Corporate proxies can inspect outbound file uploads and POST requests initiated by bots, terminating connections that attempt to transfer unencrypted PII, credit card numbers, or proprietary source code.
Proxy authentication protocols
We support Basic Auth, Digest Auth, Kerberos/SPNEGO, and mTLS proxy authentication. Proxy credentials are held in hardware security modules and never exposed in cleartext.
Troubleshooting TLS handshakes
Use the built-in diagnostic tool plannix-bot doctor --network to test TLS certificate chain integrity, OCSP stapling, and proxy connectivity before running tasks.