> ## Documentation Index
> Fetch the complete documentation index at: https://docs.safesquid.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Proxy Chain
> Deploy SafeSquid behind a parent proxy with proxy chaining, HTTPS inspection, and request forwarding for enterprise integration.
# Forward client traffic through a parent proxy
Use SafeSquid as a child proxy in front of a corporate (parent) proxy. A simple configuration in SafeSquid forwards all client requests to the parent proxy. SafeSquid can still perform HTTPS inspection and policy enforcement before forwarding; the parent handles upstream connectivity and any corporate policy.
Traffic flows from the client through the child SafeSquid to the parent proxy, then to the internet:
```mermaid theme={null}
flowchart LR
Client[Client browser]
Child[Child SafeSquid]
Parent[Parent proxy]
Internet[Internet]
Client --> Child
Child --> Parent
Parent --> Internet
```
Example scenarios:
Here am using two proxy servers as SafeSquid only
My client (Browser)## 's network IP - 192.168.0.27
My Child Proxy## 's network IP - 192.168.27.50 (with no direct internet Access)
My Parent Proxy## 's network IP - 192.168.27.100
**Configuration on child proxy:**
1. Deploy SafeSquid proxy
2. Enabling SSL inspection in SafeSquid
3. Downloading ROOT CA certificate from SafeSquid
4. Deploy certificate in client browsers.
5. Enable forwarding to parent proxy using forwarding section
**Configuration on Parent proxy:**
Deploy SafeSquid, it is up and running, no extra configuration required in parent proxy
## Prerequisites
Enable HTTPS inspection on child proxy (optionally on parent proxy also). Check our document to configure HTTPS inspection on SafeSquid - [How to configure HTTPS inspection](/SSL_Inspection)
Import SafeSquid child proxy ROOT CA in client browser
Note: No configuration required on Parent Proxy server. Just deploy the parent proxy and make sure that it is up and running.
## Configure proxy chain in SafeSquid
Access the [SafeSquid Configuration Portal](/Configuration_Portal).
### Open Configure page
### Open Application Setup → Proxy chain
### Enable Global section
### Open Forwarding proxies and add an entry
In the example: my upstream proxy ip: 192.168.27.100
In example: my upstream proxy listening on port 8080
### Test proxy chain connectivity
### Save configuration
When the administrator clicks Save config, a prompt asks for confirmation to store the configuration in the cloud.
Select Yes only in below cases:
to reuse this configuration in other SafeSquid instances.
if the total configuration in all sections is completed and validated.
Otherwise select No and click on submit.
## Verification and Evidence
* **Interface Checks**: In [Configuration Portal](/Configuration_Portal), open Application Setup → Proxy chain. Confirm Global is enabled and the forwarding proxy entry shows the correct parent IP and port.
* **Log Analysis**: Check SafeSquid access logs for requests showing the parent proxy as upstream; connection failures to the parent appear in logs with connect errors.
* **Performance Validation**: From a client behind the child proxy, browse an external site; traffic should succeed and appear in both child and parent proxy logs.
## Next steps
* [Forward Proxy](/Forward_Proxy) for explicit proxy without chaining.
* [SSL Inspection](/Configure_HTTPS_Inspection) for HTTPS inspection on the child proxy.
* [Troubleshooting](/Troubleshooting) if connectivity or parent proxy errors occur.
## Related topics
- [TCP Proxy](/use_cases/scaling_and_high_availability/tcp_proxy.md)
- [Choose an Architecture](/deployment/choose_an_architecture.md)
- [Integrations](/admin_guide/start_here/integrations.md)
- [Architecture and request pipeline](/admin_guide/start_here/architecture.md)
- [Forward proxy](/admin_guide/infrastructure_and_access/proxy_chain.md)