Uploaded image for project: 'Bitbucket Cloud'
  1. Bitbucket Cloud
  2. BCLOUD-11099

Push having problem of Authorization failed with correct credential. (BB-12392)

XMLWordPrintable

      I am facing problem while pushing with correct credential and its shows authorization failed most of the time. For every push its taking 10-15 tries which is very irritating.
      Sometimes commit got pushed but console shows an error for authorization failed, I am helpless please help me for this regard

        1. push error
          3 kB

            [BCLOUD-11099] Push having problem of Authorization failed with correct credential. (BB-12392)

            arun.chauhan added a comment -

            Attachment push error has been added with description: Originally attached to Bitbucket issue #11099 in site/master

            arun.chauhan added a comment - Attachment push error has been added with description: Originally attached to Bitbucket issue #11099 in site/master

            ifihear added a comment -

            i am seing this issue, can pull but on push it say authorization failed..

            ifihear added a comment - i am seing this issue, can pull but on push it say authorization failed..

            Jesse Yowell (Inactive) added a comment -

            Thanks for your patience all, if you still see this occurring, please contact us or reply to this thread.

            Jesse Yowell (Inactive) added a comment - Thanks for your patience all, if you still see this occurring, please contact us or reply to this thread.

            Legacy Bitbucket Cloud User (Inactive) added a comment -

            I just was able to push up code on my first try. I'll let you know if I run into the problem again, but so far so good.

            Legacy Bitbucket Cloud User (Inactive) added a comment - I just was able to push up code on my first try. I'll let you know if I run into the problem again, but so far so good.

            Daniel Goldman added a comment -

            That resolved it for us - thanks Jesse!

            Daniel Goldman added a comment - That resolved it for us - thanks Jesse!

            Jesse Yowell (Inactive) added a comment -

            We just updated the configuration on our end – can you guys test and verify?

            Jesse Yowell (Inactive) added a comment - We just updated the configuration on our end – can you guys test and verify?

            luisangelsm added a comment -

            Thank you for keeping us updated Jesse

            luisangelsm added a comment - Thank you for keeping us updated Jesse

            Jesse Yowell (Inactive) added a comment -

            Good news everyone! We found the source of the issue and we'll begin repairing this shortly. We pinpointed the cause to be part of the configuration for the new hardware we rolled out in late February. This configuration piece contained some essential authorization information for hgweb on older repos, so that is why older repos were being affected, but newer repos were working just fine. We'll let you know once we deploy the fix so we can resolve this!

            Jesse Yowell (Inactive) added a comment - Good news everyone! We found the source of the issue and we'll begin repairing this shortly. We pinpointed the cause to be part of the configuration for the new hardware we rolled out in late February. This configuration piece contained some essential authorization information for hgweb on older repos, so that is why older repos were being affected, but newer repos were working just fine. We'll let you know once we deploy the fix so we can resolve this!

            Ryan Williams added a comment -

            I wonder if it's timing related...probably just confirmation bias, but I had a little more luck when I pushed --debug --profile (which slowed it down that little bit)

            Ryan Williams added a comment - I wonder if it's timing related...probably just confirmation bias, but I had a little more luck when I pushed --debug --profile (which slowed it down that little bit)

            eiropst added a comment -

            The problem seems to affect only HTTPS, not SSH-connections. https://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Mercurial

            eiropst added a comment - The problem seems to affect only HTTPS, not SSH-connections. https://confluence.atlassian.com/display/BITBUCKET/Set+up+SSH+for+Mercurial

              jyowell Jesse Yowell (Inactive)
              arun.chauhan arun.chauhan
              Affected customers:
              7 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: