Python requests Can Read HTTPS_PROXY; Node Native fetch Does Not
If you store the connection URL under the standard HTTPS_PROXY variable, Python requests honors it automatically. If you use QUOTAGUARDSTATIC_URL for selective routing, pass that URL explicitly to the requests that should use QuotaGuard.
Node's built-in fetch uses Undici. Route it with an Undici ProxyAgent passed as the request dispatcher, with setGlobalDispatcher when global routing is intentional, or with Node's supported environment-proxy mode where available. Axios uses an https-proxy-agent through its httpsAgent option; node-fetch uses one through its agent option. Configure the client the app actually uses.
Databases Over Raw TCP Use QGTunnel
A PostgreSQL, MySQL, or MongoDB connection speaks raw TCP, not HTTP, so an HTTP proxy does not carry it. QGTunnel handles this layer instead.
QGTunnel intercepts the database connection and routes it through your static IPs transparently. Your driver connects to the normal host, including an external database your Replit app reaches by a connection-string environment variable, while egress arrives from the fixed pair.
Allowlist Both IPs on the Destination
Each subscription includes two static IPs in a load-balanced pair with automatic failover, and a request can exit from either address. Add both to the destination's allowlist, firewall, or security group in one pass.
Allowlisting only one means a failover to the second address starts getting rejected, which produces intermittent failures that are painful to trace.