> For the complete documentation index, see [llms.txt](https://docs.cloudback.it/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cloudback.it/troubleshooting-and-support/ip-whitelist.md). # IP Address Whitelist Configure IP address allowlisting to ensure Cloudback can access your GitHub repositories and maintain uninterrupted backup operations. > **Note**: This feature is also commonly referred to as "IP allowlisting." Both terms are used interchangeably in the industry. Cloudback requires network access to your GitHub repositories to perform automated backups and restore operations. In some cases, organizations implement IP address restrictions or allowlists to control access to their GitHub resources. If your organization uses such security measures, you'll need to add Cloudback's IP addresses to your allowlist to ensure uninterrupted service. ## When IP Allowlisting Is Required You may need to configure IP allowlisting if your organization: * Uses GitHub Enterprise Cloud with IP allowlists enabled for organization resources * Implements network-level security policies that restrict access by IP address * Experiences connectivity issues or backup failures related to network access restrictions If you're unsure whether your organization uses IP allowlists, contact your GitHub organization administrator or IT security team. ## Cloudback IP Addresses To ensure Cloudback can access your repositories, add the following IP addresses to your organization's allowlist: * `20.84.111.92` * `107.152.33.120` * `162.212.158.169` * `130.51.21.102` * `94.16.121.148` * `37.120.161.146` * `152.53.253.208` **Important**: All seven IP addresses must be added to the allowlist for Cloudback to function properly. Partial configuration may result in intermittent connectivity issues or backup failures. For step-by-step instructions on how to configure IP allowlists in GitHub, see the [GitHub documentation](https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization). ## Troubleshooting If you continue to experience connectivity issues after adding the IP addresses: * **Verify all seven IP addresses** are correctly entered in your allowlist without typos. * **Check for additional network restrictions** that may be in place at the infrastructure or firewall level. * **Review your GitHub organization settings** to ensure IP allowlists are properly configured. * **Contact Cloudback support** at for assistance. ## Learn More * [Managing allowed IP addresses for your organization](https://docs.github.com/en/enterprise-cloud@latest/organizations/keeping-your-organization-secure/managing-security-settings-for-your-organization/managing-allowed-ip-addresses-for-your-organization) - GitHub Documentation * [Contact Cloudback Support](/troubleshooting-and-support/contact-us.md) - Get help with configuration issues --- # 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://docs.cloudback.it/troubleshooting-and-support/ip-whitelist.md?ask=&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.