nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira cloud Migration Assistant not able to connect with server

Pandey Pradip

Hi Expert, we are Migrating our Server to cloud, for Test migration we installed JCMA Tools from UI, but JCMA not able to assess any App and it show not able to connect with server,

from log we can understand firewall is blocking the tool, but we are not able to understand specific domain/URL/IP which need to open in our Network/ firewall, or any proxy need to be configured in Server.

we checked with Atlassian documents but there are so many domain and IP provide, no specific Links or suggestion we are able to find for JCMA only. could you please help in to this and suggest specific IP and domain need to be open for JCMA only. as this is blocker for our migration.

Accepted answers

Taranjeet Singh

@Pandey Pradip please refer to the Step #6 in the below Jira pre-migration checklist document to find more information on what all Atlassian domains or endpoints you need to allow in your firewall.

https://support.atlassian.com/migration/docs/jira-pre-migration-checklist/

Hope it helps!

All comments

Taranjeet Singh

@Pandey Pradip please refer to the Step #6 in the below Jira pre-migration checklist document to find more information on what all Atlassian domains or endpoints you need to allow in your firewall.

https://support.atlassian.com/migration/docs/jira-pre-migration-checklist/

Hope it helps!

Pandey Pradip

Hi @Taranjeet Singh many thanks for the link,

in the link so many ip and domain are provide to open, are we need to open all for JCMA?.

eg- in link

Atlassian domains

Partner domains

IP address ranges (to many ip)

13.52.5.96/28 13.236.8.224/28 18.136.214.96/28 18.184.99.224/28 18.234.32.224/28 18.246.31.224/28 52.215.192.224/28 104.192.137.240/28 104.192.138.240/28 104.192.140.240/28 104.192.142.240/28 104.192.143.240/28 185.166.143.240/28 185.166.142.240/28

Taranjeet Singh

@Pandey Pradip I think it would be sufficient if you are able to connect to only the specific endpoints listed in step #6 (including your destination cloud site). If you still face any other domain connection issues, you should allow them on case by case basis based on what is reported in the logs in your case.

Taranjeet Singh

@Pandey Pradip Could you please accept this answer if it helped answer your queries so that other users in the community could benefit from this?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server

migration-customer-care