Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Unable to import repository from self hosted Gitea


I have self hosted Gitea server, from where cloning repositories on my local machine is working fine. But while importing Gitea repository to Bitbucket I am getting below error message.

"fatal: unable to access 'https:***.git/': Received HTTP code 403 from proxy after CONNECT
07:07:23 Remote Git clone failed: <class 'bitbucket.apps.asyncx.tasks.ImportException'>: Command failed. Return value: 128Screenshot_3.png

1 answer

0 votes

Welcome to the community!

Your local machine is using ssh to connect to the git repositories, but Bitbucket uses HTTPS, and the proxy between Bitbucket and the git server is not configured to allow that, or Gitea is not configured to support it.

Thank you Nic,

On local machine I am using HTTPS to clone repository.

Also I have imported my Gitea repository to site and it's perfectly imported.

Can you please let me know what proxy need to configure and where this need to be done.

I don't know where your proxy is, or even if there is one.  All I can tell you is that the error message says there is one between you and Gitea and it's not configured to allow you through from Bitbucket Cloud.  The message you are getting may not be from a proxy, it may be Gitea itself.  Either way, the proxy or Gitea are configured not to allow Bitbucket Cloud in.  It could well be as simple as the wrong credentials for the proxy or Gitea 

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

3,482 views 3 10
Read article

Atlassian Community Events