Importing the repository from self-hosted Gitlab

[Saso]

Hi!

After trying to import the repository from a self-hosted Gitlab repository, I am getting the error below. Before I submit the importing, I also get the error "No repository exists at that URL.", but as far as I read, that's not an issue if you use authorization.

=====

Your import has failed. For more information, check the log below. You can also try your import again.

07:16:17 git import for: **https://some.domain/path/torepo.git**
07:16:17 Cloning **https://some.domain/path/torepo.git**...
07:16:17 Cloning into bare repository '**placeholder for group/repo**'...
07:16:17 fatal: unable to access '**https://some.domain/path/torepo.git**/': Peer's Certificate issuer is not recognized.
07:16:18 Remote Git clone failed: <class 'bitbucket.apps.async.tasks.ImportException'>: Command failed. Return value: 128

=====

So I tried to clone it locally and I also got this error, but when I enabled sslVerify to the git config, it was working locally. So what's the correct setting in order to import the repository?
It is working fine against Github.
Do I need to use some other specific credentials for authorization?

PS: We use Letsencrypt certificate at the self-hosted Gitlab domain, but this shouldn't be an issue right?

Thank you!

[Marcus Shane]

We are starting our conversion from Bitbucket Server to Bitbucket Cloud and we are getting the same error.

1. 07:58:09 git import for: https://{{URL}}/scm/es/active-directory.git
2. 07:58:09 Cloning https://{{URL}}/scm/es/active-directory.git...
3. 07:58:09 Cloning into bare repository '{{WORKSPACE}}/active-directory'...
4. 07:58:10 fatal: unable to access 'https://{{URL}}/scm/es/active-directory.git/': Peer's Certificate issuer is not recognized.
5. 07:58:10 Remote Git clone failed: <class 'bitbucket.apps.asyncx.tasks.ImportException'>: Command failed. Return value: 128

I tried reviewing this documentation: https://support.atlassian.com/bitbucket-cloud/docs/import-or-convert-code-from-an-existing-tool/ and it did not work.

Can anyone else provide any guidance?

Thanks.

[Ritesh Srivastava]

i am facing this issue while importing from my in-house hosted community GitLab to BitBucket cloud.

Please suggest the possible issue so that we can migrate the repo.

We're getting things warm and cozy for your code.

Your import has failed. For more information, check the log below. You can also try your import again.

1. 19:46:17 git import for: https://gitlab.xxxxxxxx.com
2. 19:46:18 Cloning https://gitlab.xxxxxxxx.com...
3. 19:46:18 Cloning into bare repository 'QTX067/movement-mbaprocess.git'...
4. 19:46:20 fatal: https://abc@gitlab.xxxxxxxx.com/info/refs not valid: is this a git repository?
5. 19:46:20 Remote Git clone failed: <class 'bitbucket.apps.asyncx.tasks.ImportException'>: Command failed. Return value: 128

[Mohamed Sharfaz Sairaz]

I am having same issue. Have self hosted Bitbucket server and trying to import getting same error.

15:46:20 git import for: https://{{URL}}/scm/syb/apibundle.git

15:46:21 Cloning https://{{URL}}/scm/syb/apibundle.git...

15:46:21 Cloning into bare repository 'team/apibundle'...

15:46:21 fatal: unable to access 'https://{{URL}}/scm/syb/apibundle.git/': Peer's Certificate issuer is not recognized.

15:46:22 Remote Git clone failed: <class 'bitbucket.apps.async.tasks.ImportException'>: Command failed. Return value: 128

I disable the git SSL verify check also try to update CA path and info. Still getting same error

[Ana Retamal]

Hi Saso, welcome to the Community!

Are you still experiencing that issue? If so, can you answer the following questions to help us troubleshoot?:

1. Have you checked the logs in verbose mode? Did you find any additional error messages?
2. Have you tried disabling Letsencrypt and see if it works?

Let us know!

Ana

[Saso]

Hi!

I still haven't resolved the issue.

1. We are actually using BitBucket cloud solution so I can not really see the logs. And I can clone it localy, over HTTPS perfectly. Can I see some more logs from the BitBucket side?

2. Could Letsencrypt cause issues? Should we try http only?

Br, Saso