Tinyproxy Direct Connections vs. Upstream Parent Proxies

Tinyproxy can open the destination connection itself. A second proxy is optional:

client → Tinyproxy → website

In that arrangement, no parent Upstream rule is needed. Tinyproxy's machine needs a working route and destination-name resolution, and its client and destination policies still govern the request.

A network that requires a corporate gateway can use another path:

client → Tinyproxy → parent proxy → website

The Upstream configuration selects that parent. It is useful when the parent supplies required network access or an intended onward exit. It does not start another service automatically.

The client continues to use Tinyproxy's listening address in both cases. Moving from direct forwarding to a parent changes Tinyproxy's onward route; it does not turn the parent's address into Tinyproxy's local listener.

Also keep the public exit separate from the machine's local address. Direct connections can leave through NAT, and two proxies on one network can share the same public exit. Adding a second hop does not by itself guarantee a different IP address at the website.