You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When I try to use the bitbucket migration assistant to migrate from Bitbucket server 7 to cloud I receive this error message when trying to set the "Migrate from" field.
"The base URL did not validate, check and enter it again. If you feel this is correct, please contact your support team."
I initially used the URL we use internally, however this name resolves to an IP address that only works internally, my migrations failed using this name (except for users), I am assuming this is because the cloud was not able to use this URL to connect to our bitbucket server directly.
For the purpose of integrating our Bitbucket server instance with JIRA cloud, we have already created another DNS name that resolves to an externally visible IP address for our bitbucket server. We are not able to use this address internally, it is firewalled so that it is only accessible from the Atlassian cloud. This works fine for the purpose of JIRA cloud to Bitbucket server (on-premises) integration. It seems that is should be able to be used by the bitbucket cloud / migration.atlassian.com domain ?
Is there a reason why our external address is failing validation, and our internal address is passing (when it should probably not?) and what can I do to make our bitbucket server accessible to the migration tool?
Hi @Jason Roos,
The URL you enter in that field needs to be the base URL configured for this instance in the setting mentioned in the following doc (not just a URL that you can use to access the instance):
If you don't have access to these settings, please ask one of the Administrators of your Bitbucket Server instance to let you know what that is.
The BCMA doesn't actually care if the URL provided is something that it can't resolve. Regardless of how many network paths are in place, even if they work or not, the BCMA is asking your server to confirm if the base URL provided matches how the instance itself is configured. It is not looking for a valid network path, but rather a confirmation of configuration.
Please check the base URL of your Bitbucket Server as per the doc I shared and feel free to let me know if using that URL works for you or if you face any other issues.