GitHub IP Allow List
If your GitHub organisation has the IP Allow List feature enabled, Frappe Cloud servers may be blocked from making authenticated GitHub API calls and cloning repositories during deployments, even when valid credentials are provided.
When Frappe Cloud tries to access repositories available to the connected GitHub user, you may receive a 403 Forbidden error like:
{
"message": "Although you appear to have the correct authorization credentials, the organisation has an IP allow list enabled, and your IP address is not permitted to access this resource.",
"documentation_url": "https://docs.github.com/rest/apps/installations#list-repositories-accessible-to-the-user-access-token",
"status": "403"
}
What Does This Affect?
When Frappe Cloud IP addresses are not allowed by GitHub, the following features may stop working:
- Repository Dropdown: The repository list in the Frappe Cloud dashboard may show “No results found”.
- Deployments: Build servers may not be able to clone private repositories.
- Background Jobs: Jobs that fetch releases from GitHub may fail.
What Is GitHub’s IP Allow List?
GitHub’s IP Allow List is a security feature that restricts access to organisation resources, including repositories and APIs, to only approved IP addresses.
Availability
| GitHub Plan | IP Allow List Available |
|---|---|
| GitHub Free (personal) | ❌ No |
| GitHub Team | ❌ No |
| GitHub Enterprise Cloud | ✅ Yes |
| GitHub Enterprise Server | ✅ Yes |
| GitHub Advanced Security (standalone) | ❌ No |
Note
IP Allow List is available only with GitHub Enterprise Cloud and GitHub Enterprise Server.
Where Is IP Allow List Configured?
You can manage the IP Allow List settings from your GitHub organisation security settings:
https://github.com/organizations/{your-org}/settings/security
Navigate to:
Organisation Settings → Security → IP allow list
Root Cause
Frappe Cloud production and build servers use fixed public IP addresses. If these IPs are not added to your organisation’s GitHub IP Allow List, GitHub blocks all API requests and repository clone operations coming from Frappe Cloud.
IPs to Whitelist
Frappe Cloud Production Server
Used for GitHub API operations such as repository listing, branch fetching, and webhook processing.
| IP Address | Purpose |
|---|---|
139.59.79.221 |
Frappe Cloud production server |
Build Servers
Used for cloning repositories during app deployments.
| IP Address | Purpose |
|---|---|
13.205.88.211 |
Build server |
43.205.115.209 |
Build server |
13.127.110.154 |
Build server |
64.227.148.209 |
Build server |
139.59.9.202 |
Build server |
64.227.183.30 |
Build server |
Steps to Whitelist Frappe Cloud IPs
- Open your GitHub organisation security settings.
- Navigate to IP allow list.
- Click Add.
- Add each Frappe Cloud IP address with a descriptive label.
- Save the changes.
- Repeat the process for all required IP addresses.
After adding all IPs, return to the Frappe Cloud dashboard and retry connecting your GitHub app. The repository dropdown should now display available repositories.
Notes
- These IP addresses belong to Frappe Cloud’s shared infrastructure and are common for customers using the platform.
- If your site is hosted on a dedicated or private Frappe Cloud cluster, the IP addresses may be different. Contact Frappe Cloud support to confirm the correct egress IPs.