> For the complete documentation index, see [llms.txt](https://doc.sk5data.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.sk5data.com/faq/common-questions/why-cant-i-connect-after-adding-an-ip-to-the-whitelist.md).

# Why Can't I Connect After Adding an IP to the Whitelist?

If you still cannot connect after adding an IP to the whitelist, check whether the IP address you added matches the actual public outbound IP used to make the proxy request.

**Common Scenarios:**

* **Local Computer:** Add the public outbound IP address of the computer you are using to access the internet.
* **Server:** Add the server's public outbound IP address, not your local computer's IP.
* **Dynamic Public IP:** If your public outbound IP changes, you need to add the new IP address to the whitelist.

**How to Fix It:**

1. Go to the **IP Whitelist** page for the corresponding proxy product.
2. Verify that the whitelisted IP matches your actual public outbound IP.
3. If the IP has changed, add the new IP address and save your changes.
4. Run the proxy connection test again.

If the whitelist is correct but you still cannot connect, check the proxy hostname, port, protocol, and plan status.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doc.sk5data.com/faq/common-questions/why-cant-i-connect-after-adding-an-ip-to-the-whitelist.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.