Error importing bitbucket repository from URL - unable to access [FILTERED] Failed to connect to X port Y after Z ms: Couldn't connect to server

Summary

I'm getting an error when I try to import a bitbucket server repository using the URL import. Cloning from a local machine works fine, but using the Gitlab UI it fails.

Steps to reproduce

• Spin up a bitbucker server
• Create a simple repository
• Make sure that cloning in a terminal works fine
• Import the repository to gitlab.com using the import project from repository by URL feature

Example Project

• https://gitlab.com/b_freitas_ultimate_group/tests-and-troubleshooting/ticket-460123-bitbucket-import-error (GitLab team members may ask for access)

What is the current bug behavior?

I'm getting the error below:

"Error importing repository XXXX.git into XXXX - 13:creating repository: cloning repository: exit status 128, stderr: \"fatal: unable to access [FILTERED] Failed to connect to XXX port XXXX after 130282 ms: Couldn't connect to server

What is the expected correct behavior?

The import should work

Relevant logs and/or screenshots

Got the details with the project import status API:

{
"id": 51356519,
"description": "",
"name": "Ticket 460123 - BitBucket Import Error",
"created_at": "2023-10-18T17:00:31.710Z",
"import_status": "failed",
"import_type": "git",
"correlation_id": "01HD1VPM6M4PWFM1ETCYT4D5YY",
"failed_relations": [],
"import_error": "Error importing repository [FILTERED] into [FILTERED] - 13:creating repository: cloning repository: exit status 128, stderr: \"fatal: unable to access [FILTERED] Failed to connect to [FILTERED] port [FILTERED] after 130282 ms: Couldn't connect to server\\n\".",
"stats": null
}

Possible fixes