$ git clone https://username@bitbucket.org/username/repo.git\\
      Cloning into 'repo'...
      fatal: unable to access 'https://username@bitbucket.org/username/repo.git/': The requested URL returned error: 500

      Since yesterday servers don't work. Other people have this issue too, i.e. in comments BCLOUD-7994 .

            [BCLOUD-14039] The requested URL returned error: 500

            Attachment 534296359-Screen%20Shot%202017-03-26%20at%2012.59.03%20AM.png has been added with description: Originally embedded in Bitbucket issue #14039 in site/master

            IdeeZumApps added a comment - Attachment 534296359-Screen%20Shot%202017-03-26%20at%2012.59.03%20AM.png has been added with description: Originally embedded in Bitbucket issue #14039 in site/master

            Attachment 3712355980-Capture.PNG has been added with description: Originally embedded in Bitbucket issue #14039 in site/master

            akash_kava added a comment - Attachment 3712355980-Capture.PNG has been added with description: Originally embedded in Bitbucket issue #14039 in site/master

            Just wanted to say, visiting the link id.atlassian.com as mentioned in the 4th post fixed this issue for me this morning cheers

            abrahamTourdex added a comment - Just wanted to say, visiting the link id.atlassian.com as mentioned in the 4th post fixed this issue for me this morning cheers

            I've created a new issue here and marked it as critical: BCLOUD-16454

            Andrew Bodis added a comment - I've created a new issue here and marked it as critical: BCLOUD-16454

            I am also having the same issue with our pipelines. No changes made to the pipeleines:

            + GIT_LFS_SKIP_SMUDGE=1 git clone --branch="some_branch_name" --depth 50 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/xxxxx/xxxxxx.git $BUILD_DIR ; git reset --hard xyxyxyxyxyxyx ; git remote set-url origin git@bitbucket.org:xxxxxxxxxxxx/xxxxxxx.git
            Cloning into '/opt/atlassian/pipelines/agent/build'...
            remote: unable to authorize current user, internal server error
            fatal: unable to access 'https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/xxxxxxxxx/xxxxxxx.git/': The requested URL returned error: 500
            

            Shail Choksi added a comment - I am also having the same issue with our pipelines. No changes made to the pipeleines: + GIT_LFS_SKIP_SMUDGE=1 git clone --branch= "some_branch_name" --depth 50 https: //x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/xxxxx/xxxxxx.git $BUILD_DIR ; git reset --hard xyxyxyxyxyxyx ; git remote set-url origin git@bitbucket.org:xxxxxxxxxxxx/xxxxxxx.git Cloning into '/opt/atlassian/pipelines/agent/build'... remote: unable to authorize current user, internal server error fatal: unable to access 'https: //x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/xxxxxxxxx/xxxxxxx.git/': The requested URL returned error: 500

            I'm having problems with pipelines and it seems to be related to this. Here's the output, of the very first step:

            Andrew Bodis added a comment - I'm having problems with pipelines and it seems to be related to this. Here's the output, of the very first step: GIT_LFS_SKIP_SMUDGE=1 git clone --branch="feature/docker-pipelines" --depth 50 https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/xxx/yyy.git $BUILD_DIR ; git reset --hard 3fd2599c6720f0c10207a50f0c67586b2aa7c9e4 ; git remote set-url origin git@bitbucket.org:xxx/yyy.git Cloning into '/opt/atlassian/pipelines/agent/build'... remote: unable to authorize current user, internal server error fatal: unable to access ' https://x-token-auth:$REPOSITORY_OAUTH_ACCESS_TOKEN@bitbucket.org/xxx/yyy.git/': The requested URL returned error: 500
            Alastair Wilkes made changes -
            Status Original: GATHERING IMPACT [ 12072 ] New: CLOSED [ 6 ]

            We released a fix for this issue last night. If your issue persists, file a new issue and we'll investigate.

            Alastair Wilkes added a comment - We released a fix for this issue last night. If your issue persists, file a new issue and we'll investigate.

            We've received additional issue reports. We are working on identifying the root cause.

            Alastair Wilkes added a comment - We've received additional issue reports. We are working on identifying the root cause.

            Thanks for the response. Hmm. So neither your Atlassian account password nor an app password works for git interactions? Are you sure you're not using stored credentials? Are you using the command line or a tool like SourceTree?

            If you can log into bitbucket.org with your Atlassian account email and password, your Bitbucket username and Atlassian account password (or app password) should work for basic auth.

            Alastair Wilkes added a comment - Thanks for the response. Hmm. So neither your Atlassian account password nor an app password works for git interactions? Are you sure you're not using stored credentials? Are you using the command line or a tool like SourceTree? If you can log into bitbucket.org with your Atlassian account email and password, your Bitbucket username and Atlassian account password (or app password) should work for basic auth.

              dtao dtao
              1fa0315dbaca damplate
              Affected customers:
              2 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: