> ## Documentation Index
> Fetch the complete documentation index at: https://docs.2extract.com/llms.txt
> Use this file to discover all available pages before exploring further.

# My proxy is not connecting (Timeout / Connection Refused)

> What to do when you can't establish a connection to our proxy gateway.

Connection Timeouts or "Connection Refused" errors typically indicate a network-level issue between your machine and our proxy gateway. Here’s how to troubleshoot it.

### Step 1: Verify Host and Port

First, ensure you are using the correct host and port number for your proxy.

* **Host:** `proxy.2extract.net`
* **Port:** `5555`

A common mistake is using the wrong port number or misspelling the host.

### Step 2: Check Your Firewall

Your local machine, server, or cloud provider (like AWS or Google Cloud) may have a firewall that blocks outgoing connections to specific ports.

1. **Check your local firewall rules** (e.g., Windows Firewall, `ufw` on Linux).
2. **Check your cloud provider's security group rules.** Make sure that outgoing (egress) traffic is allowed to the TCP port your proxy uses.

### Step 3: Use a Network Diagnostic Tool

You can use a built-in tool from your command line to check for basic connectivity.

<CodeGroup>
  ```bash macOS / Linux theme={null}
  nc -zv proxy.2extract.net 5555
  ```

  ```powershell Windows (PowerShell) theme={null}
  Test-NetConnection -ComputerName proxy.2extract.net -Port 5555
  ```
</CodeGroup>

* If the connection succeeds (`nc` shows `succeeded`, PowerShell shows `TcpTestSucceeded: True`): your network path is fine. The problem is likely in your script's configuration.
* If the command hangs or reports a failure: there is a network block somewhere between you and our gateway. Re-check your firewall rules.

<Info>
  If you've checked all of the above and the issue persists, please contact our **[Support Team](mailto:support@2extract.com)** and provide them with the output of your diagnostic tests.
</Info>