Summary

The article below provides guidance on effectively utilizing 'Connect to Cloud' or 'Choose Cloud Site' when connecting to the destination cloud site during the creation of a migration plan.

Overview

When migrating data, whether it's from a server to the cloud or from one cloud to another, the initial crucial step involves establishing a connection to the target cloud site using either the ‘Connect to Cloud' or 'Choose Cloud Site' option. Several key steps must be completed before initiating the connection to the destination cloud.

Server to cloud Migration

1. Please refer to the documentation IP addresses and domains for Atlassian cloud products and make sure that your network, firewall, or proxy grants access to the given IP addresses and URLs by contacting your network or security teams.

2. Make sure the user who is trying to create the migration plan is:

   1. Part of the Jira-administrators group on the Jira server or confluence-administrators group on the Confluence server.

   2. The user should have a valid trusted domain and email address on the source server instance.

   3. On the destination, the user should be part of the site-admin/org-admin group

3. Make sure the Jira/Confluence server Base URL is a valid one as we will be using the same URL in the Migrated from section during the migration plan creation step 

   Reference for "Migrated from" section mentioned above

   

Cloud to cloud Migration

1. To migrate data between two cloud sites within the same organization, you must have site admin privileges for the destination site.

2. If you intend to migrate to a site within a different organization, you must hold organization admin rights for both cloud sites which is part of the migration.

Resolve Connection Errors to the Destination Cloud

1. Check the log file atlassian-jira.log/atlassian-confluence.log on the respective Jira or Confluence server

2. If you are seeing any connection error to the URLs mentioned in the documentation IP addresses and domains for Atlassian cloud products, please make sure all IPs and domains are excluded from the firewall

3. If you have configured the Outbound proxy on your server then please make sure you have added JVM arguments suggested in the article How to Configure Outbound HTTP and HTTPS Proxy for your Atlassian application

4. If you are getting any SSL-related errors mentioned below in Jira/Confluence log:

   PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target

   then please check the connection issue by using the command below 

   java -Djavax.net.debug=ssl SSLPoke api-private.atlassian.com 443

   curl -v https://api-private.atlassian.com

   here, you can find the domain name from the log. For more details please refer to the documentation Unable to connect to SSL services due to the "PKIX Path Building Failed" error

5. After following the above article and if you are still getting errors, you can try to download the certificate using the command below and install it on Java truststore (typically $JAVA_HOME/lib/security/cacerts ). The truststore contains a list of all known Certificate Authority (CA) certificates, and Java will only trust certificates that are signed by one of those CAs or public certificates that exist within that truststore. 

   openssl s_client -connect api.atlassian.com:443 -servername api.atlassian.com < /dev/null | sed -ne '/-BEGIN CERTIFICATE-/,/-END CERTIFICATE-/p' > api.crt

6. If you are not seeing any connection in the Jira/Confluence log, but still getting errors then please try to connect to the cloud site from a different browser or browser in incognito mode to confirm browser cache/cookies are not causing the issue

7. If the issue still persists, please reach out to Atlassian support and share the logs generated by following the steps below:

   1. Navigate to Administration » System » Logging and profiling.

   2. Click Configure logging for another package link.

   3. Add org.apache.http and set it to TRACE level

   4. mark the logs as "Issue recreation start here"

   5. After that go to Migration Dashboard

   6. Open Browser developer tools as we need to trace the request & response while recreating the issue

   7. Try to recreate the error 

   8. Collect HAR file from developer tool

   9. Generate and upload the support.zip file 

   10. Navigate to Administration » System » Logging and profiling.

   11. Remove org.apache.http

Related links for extra reading:

Working with Confluence Logs
Configuring Logging in Confluence
How to enable debug logging for outgoing http connections in Jira
Connection Error while using connect to cloud option in JCMA/CCMA