Gunicorn bind Does Not Configure an Outbound Proxy
Find the Python client making outbound calls instead of using inbound server and forwarded-header settings as proxy controls.
Gunicorn's bind address accepts incoming application requests. It does not select a forward proxy for API calls made by that application.
Find the outbound consumer—Requests, HTTPX, an SDK or subprocess—and configure its public proxy interface or the environment it reads. A correctly configured Requests Session does not reconfigure another SDK.
Check the worker's effective launch environment against deployment settings. An interactive shell can hold different values. Keep credentials in the established secret mechanism and avoid environment dumps exposing them.
Gunicorn's trusted forwarded-header options interpret inbound metadata; they do not send new API calls back through that intermediary.
For an unexpected exit, trace the outbound connection. For public API requests allowed through public intermediaries, the free proxy list offers candidates to configure through that outbound client's supported protocol and interface. Visitor address, Gunicorn listener, local server source and remote proxy exit can all differ. Keep those observations separate instead of making one bind setting answer all four questions.