Skip to main content

Allowlisting Vansah IP Addresses for Plugin Migrations

Find Vansah’s regional migration IP addresses and learn how your Atlassian administrator can allow access when Jira uses an IP allowlist.

If your organization restricts Jira access with an IP allowlist, add the Vansah migration service’s addresses for your region so its requests can reach Jira. An IP allowlist is a list of approved network addresses.

This can affect migration setup and requests made with Jira credentials, including related Jira custom-field setup. A connection problem in one of these features does not necessarily mean the rest of Vansah is unavailable.

Before you begin

  • Ask an Atlassian organization admin to review the allowlist for the correct Jira site.

  • Confirm your Jira site’s pinned data residency region. Use that region to select addresses below, rather than your personal location.

  • If your site is not pinned, the region is unclear, or your region is not listed, contact Vansah to confirm the addresses to use.

Review the Jira IP allowlist

  1. Open Atlassian Administration and select your organization.

  2. Go to Security → Device security → IP allowlists.

    IP allowlist under Device security in Atlassian Administration
  3. Check whether an active allowlist applies to the Jira site used for the migration.

  4. Add all the Vansah addresses for the applicable region to the relevant allowlist, preserving the organization’s existing entries. Save the changes and confirm that the intended policy is active.

  5. Retry the connection or setup step that failed.

For Atlassian’s current requirements and instructions, see Specify IP addresses for app access.

Vansah migration service IP addresses

Add each address listed for your region as a separate IP address entry.

Jira pinned region

IP addresses

Europe, including Germany and Denmark

144.126.245.245
​139.59.206.53
​64.226.103.163
​164.90.177.88

United Kingdom

159.65.215.8
​142.93.44.22

United States, served from New York

45.55.126.122
​45.55.121.242
​138.197.27.146
​143.198.26.209

Singapore

157.230.194.47
​188.166.187.239

Australia, served from Sydney

170.64.249.138
​170.64.241.74
​170.64.216.113
​170.64.163.30

Canada, served from Toronto

209.38.12.50
​159.203.26.46

These addresses may change as Vansah’s network configuration changes. Recheck this list before a migration and keep the required access in place throughout it.

If the connection still fails

You may see a message such as Could not find authentication data on request.

Example authentication error during connection setup

This message can have more than one cause. Check the following before retrying:

  • The allowlist applies to the correct Jira site and includes every address for the correct region.

  • The Jira credentials or token used for the setup are valid, and the account has the required permissions.

  • The setup uses the correct Jira site and Jira space.

If the problem continues, contact Vansah with the Jira site URL, pinned region, exact error, and the setup step that failed. Do not include passwords or API tokens.

After the migration

Ask your administrator to review whether the migration entries are still needed. Confirm whether any ongoing integration, such as Jira custom-field access, depends on them before removing entries.

Did this answer your question?