GitKraken does not host Jira Server or Jira Data Center products.
If your firewall or proxy server restricts outbound connections, add the IP addresses listed below to your allow list. This configuration enables GIJ Cloud applications to connect to your private git server (GitHub Enterprise, GitLab CE/EE, Microsoft TFS, Azure DevOps Server, Gerrit, Bitbucket Server, or a plain git server).
Alternatively, use the Webhook indexing feature to avoid incoming API requests.
On this page:
- Configure allow list for self-hosted git repositories
- Open required ports
- Configure allow list for GitHub.com, Azure DevOps Repos, and GitLab.com
- Verify network reachability
- Use webhook indexing for private networks
Configure Allow List for Self-Hosted Git Repositories
GIJ Cloud supports Atlassian’s Data Residency hosting model. Jira Cloud instances can be assigned to specific geographic regions. GIJ Cloud currently supports hosting in the USA and EU. Customers not pinned to a specific region are assigned to the Global region (hosted in the USA). All applications and data are hosted in Amazon Web Services (AWS). For more information, see the Trust & Security page.
To find your geographic region, see How do I find my app data.
Global Hosted Customers (US-East-1)
Add these IP addresses for customers hosted in the Global region (Northern Virginia, USA AWS region US-East-1):
| Server | IP address |
|---|---|
| App server 0 | 52.73.151.196 |
| App server 1 | 54.156.212.90 |
European Union Hosted Customers (EU-West-1)
Add this IP address for customers hosted in the EU stack (Ireland, EU-West-1):
| IP address |
|---|
| 18.202.139.125 |
European Union Hosted Customers (EU-Central-1)
Add this IP address for customers hosted in the EU stack (Frankfurt, Germany, EU-Central-1):
| IP address |
|---|
| 18.156.13.64 |
USA Hosted Customers (US-East-2)
Add these IP addresses for customers hosted in the US stack (Ohio, USA AWS region):
| Server | IP address |
|---|---|
| App Server 0 | 18.218.206.0 |
| App Server 1 | 18.218.116.230 |
Southeast Asia Hosted Customers (AP-Southeast-1)
Add this IP address for customers hosted in the Southeast Asian stack (Singapore):
| IP address |
|---|
| 13.215.67.222 |
Australia Hosted Customers (AP-Southeast-2)
Add these IP addresses for customers hosted in the Australia stack:
| Server | IP address |
|---|---|
| App Server 0 | 52.65.83.20 |
| App Server 1 | 13.237.217.178 |
Open Required Ports
Open the following ports to allow GIJ Cloud applications to index your self-hosted git repositories:
| Protocol | Port | Notes |
|---|---|---|
| HTTPS | 443 | Most common configuration |
| HTTP | 80 | Rarely used |
| SSH | 22 | Required only when using SSH keys for authentication |
Example: If your self-managed GitLab or GitHub Enterprise uses HTTPS, open only port 443.
Configure Allow List for GitHub.com, Azure DevOps Repos, and GitLab.com
GitHub.com, Azure DevOps Repos, and GitLab.com provide enterprise-level allow listing features that require additional IP addresses.
Global Region (US-East-1)
54.196.201.91, 34.228.185.171, 34.224.218.252, 3.80.89.149, 34.224.101.92, 34.224.75.91, 52.23.171.14, 54.147.140.182, 54.235.62.22, 54.175.233.217, 18.208.171.222, 54.90.148.157, 54.242.227.154, 54.209.11.3, 3.88.216.216, 3.80.49.193, 54.87.49.117, 54.174.135.57, 52.54.150.111
USA Region (US-East-2)
3.130.34.25, 18.218.122.134, 3.131.213.149, 3.143.100.15, 3.133.34.235, 18.190.109.9, 18.119.80.14, 3.14.197.223, 3.142.176.34, 3.130.151.4
Central EU Region (EU-Central-1)
3.123.136.62, 18.156.8.182, 18.198.71.138, 3.69.186.247, 3.70.82.79, 18.159.165.4, 3.125.231.184, 3.68.13.136, 3.67.63.5, 52.58.106.61
Western EU Region (EU-West-1)
34.247.19.97, 54.72.243.188, 52.210.99.19, 54.76.253.102
Southeast Asia – Singapore Region
18.140.19.30, 18.143.232.103, 54.151.179.195, 18.138.219.190
Australia Region
54.206.176.144, 3.105.72.140, 52.64.118.63, 13.238.136.180
If you use these IP addresses for allow listing, contact GIJ Cloud Support so we can notify you if these addresses change.
Verify Network Reachability
Your self-hosted git server must have a public address that the GIJ Cloud indexing service can reach.
If your git server sits behind a firewall, add the indexing service IP addresses to your allow list (see Configure allow list).
If your git server is accessible only through a private intranet or VPN, the GIJ Cloud indexing service cannot reach it—even with an allow list. Use webhook indexing instead.
Reachability examples:
| Reachable? | Example |
|---|---|
 |
https://git.corp.com/repository/widget-production.git — Hosted git repository |
|
https://git.corp.com — Git server running GitHub/GitLab |
|
https://gitlab.corp.com:8088 — Server on non-standard port |
|
http://52.123.19.12 — Server without DNS |
 |
192.168.1.92 — Private IP address |
|
git.corp — Private network hostname |
Webhooks Indexing Integration for Private Networks
Webhook indexing supports indexing commits and pull requests using webhook metadata. This approach keeps your git server in a private network while sending sufficient git metadata to associate activity with Jira issues.
Limitations:
- Cannot view source code (Jira issue ➜ Git Commits tab ➜ View full commit)
- Cannot create branches or pull/merge requests from within Jira
For more information, see:
GIJ Cloud Apps
Get Support
Contact GIJ Cloud Support for help connecting self-hosted git servers or repositories.
Last updated: December 2025
