Whitelist IP addresses for on-premise development systems


If you are integrating with an on-premise development system like Jira Server or Microsoft Team Foundation Server, you may need to whitelist Aha! in your firewall so that Aha! can make connections to your server to create records. The IP addresses that Aha! will use depend upon your account. An account administrator can find the IP address set for your account on this page: https://secure.aha.io/settings/account/security

You must whitelist all of the IP addresses in the set that applies to your account. If your company has multiple accounts that use both sets it may be necessary to whitelist all eight addresses.

Set 1:

  • 23.22.45.22
  • 54.84.62.26
  • 52.7.117.222
  • 52.5.204.179

Set 2:

  • 54.84.9.164
  • 35.171.201.123
  • 18.233.118.192
  • 18.232.220.143


All traffic is HTTPS (port 443). You may specify a custom port (other than 443) in the URL when configuring the URL for the on-premise server in Aha!

HTTPS webhook traffic from the development system to Aha! (outbound from the on-premise network) will go to the same four IP addresses. It is only necessary to whitelist these IP addresses for outbound connections if you normally block outbound connections which is less common.

If you already have IP addresses whitelisted then they will not change. The new addresses only apply to newly created accounts.

Was this article helpful?
5 out of 6 found this helpful
Have more questions? Submit a request
Powered by Zendesk