problems with Github integration to Compass
Asked by Nikhil Anand:

Hi All,

We have followed all steps to integrate Github with Atlassian Compass and gave all permissions on Github but for some reason whenever I add a repository link, I get an error as **Restricted Link, try another account**   

I followed this support [link](https://support.atlassian.com/jira-cloud-administration/docs/integrate-with-github/) as well for the Github enterprise allow IP list but even after whitelisting, I am still getting the same response.  

Can you please help me out here?


Answers:
author: Josh Campbell
body: Hey Nikhil, Josh here from the product team, my team owns the GitHub integration.

First, just want to mention that the article you linked about allowing IPs is actually documentation for Jira and not Compass. Compass is a standalone product and not part of Jira so that unfortunately will not have any effect.

I want to confirm, is this GitHub Enterprise Cloud you are using? We do not support self-hosted GitHub Enterprise Server.

Also, for the repository link in question, is it in the same GitHub Organization that you connected to Compass during configuration? The integration currently supports only one GitHub Organization to attach to the Compass site but we have support for multiple on our roadmap for 2023 delivery.

Let me know if this doesn't help and we can keep digging. Also, feel free to use the Intercom chat button in the bottom right of your screen on Compass to engage with our support team at any time. Cheers Nikhil!

comments: author: Nikhil Anand
body: Hi Josh,

Yes, we are using Github Enterprise cloud and it is not a self-hosted Github Enterprise server. And yes it is the same organization that we have connected Compass to.

We do have ip firewall list applied on Github. Will that be blocking this and causing that error/statement to pop out? If yes, can you please share its IPs with me so I can get it whitelisted


author: Josh Campbell
body: Hey Nikhil so sorry for the delay, I missed your reply. Ah yes that's likely the culprit then if you have IP Allowlisting in place for GitHub Enterprise Cloud. Because Atlassian Forge runs on AWS Lambda, you will need to whitelist AWS IP ranges for this to work; [there is some more information in this ticket](https://ecosystem.atlassian.net/browse/FRGE-276) from the Forge team.


author: Dave Nicholson
body: [@Josh Campbell](/t5/user/viewprofilepage/user-id/4526760) is there a delivery ticket to watch IRT support for multiple GH orgs in Enterprise? I'll be able to get back into looking at using Compass once that's possible.


author: Josh Campbell
body: Hey Dave, no public ticket tracking for GH multi org support. Official answer is that it's coming this year! That said, I understand the importance here and it's something I'm looking to ship sooner rather than later.


author: Nikhil Anand
body: [@Josh Campbell](/t5/user/viewprofilepage/user-id/4526760)Any updates on the AWS IP Ranges that we need to whitelist? I do not see any update on the ticket that you had shared earlier!


author: Patrick Brady
body: Hey there Nikhil, there is an update from the forge (that platform our apps use) team publishing the IP ranges that forge uses that you might be able to use to configure your allowlist. <https://developer.atlassian.com/platform/forge/changelog/#CHANGE-1168>