Dropstone Docs

Network

Configure proxies and custom certificates.

Dropstone supports standard proxy environment variables and custom certificates for enterprise network environments.

Proxy

Dropstone respects standard proxy environment variables.

# HTTPS proxy (recommended)
export HTTPS_PROXY=https://proxy.example.com:8080

# HTTP proxy (if HTTPS not available)
export HTTP_PROXY=http://proxy.example.com:8080

# Bypass proxy for local server (required)
export NO_PROXY=localhost,127.0.0.1

Important:

Dropstone uses a local HTTP loopback during interactive sessions. You must bypass the proxy for localhost/127.0.0.1 to prevent routing loops.

You can configure the local bind address using CLI flags.

Authenticate

If your proxy requires basic authentication, include credentials in the URL.

export HTTPS_PROXY=http://username:password@proxy.example.com:8080

Avoid hardcoding:

Avoid hardcoding passwords in shell config. Use environment variables, your OS keyring, or a secrets manager.

For proxies that require advanced authentication (NTLM, Kerberos), front Dropstone with a local authenticating proxy (such as cntlm) and point HTTPS_PROXY at the local proxy instead.

Custom certificates

If your enterprise uses custom CAs for HTTPS connections, configure Dropstone to trust them.

export NODE_EXTRA_CA_CERTS=/path/to/ca-cert.pem

This works for both proxy connections and direct API access.

Ctrl+I