Issue #3707 closed

Abort: Authorization Failed when trying to push changes to the server

Anonymous created an issue

I recently recloned a repo from our server using the same methodology and settings through Workbench as previous clones. I am able to pull incoming changes as well as commit local changes. However, I receive an "Abort: Authorization Failed" error when trying to push those changes to the URL. I've tried both through the GUI and Mercurial interface with the same results.

Side notes, version I'm using is 2.4.1. My network password has recently changed, but that shouldn't be an issue since it has to be updated periodically and has never seen this issue. It's also up to date in the mercurial.ini file. Whenever I first began using TortoiseHg a few months ago, any change made would prompt my credentials to be entered. I solved that by saving the log-in info to the mercurial file. However, when that info is deleted, I am not prompted to enter my username/pword before preceding. I initially thought this might be the hang up, but it doesn't appear so.

Any ideas on what could be causing the failed authorization for just the push for this repo?

Comments (20)

  1. Yuya Nishihara

    hg push --debug might have a clue.

    when that info is deleted, I am not prompted to enter my username/pword before preceding.

    Just in case, check the output of hg showconfig to see if that entry is deleted completely.

  2. Brent G

    I am having the same problem. I am trying to push to a fork that I created. I am using TortoiseHg 3.0.1 64-bit on Windows 8.1.

    I enabled debug in the synchronization window. It just repeats the same authorization successful message while it is uploading data. Then it will abort part way through.

    http auth: user decatf, password *****
    using auth.hg.codeplex.com.
    for authentication
    hg.codeplex.com certificate successfully verified
    abort: authorization failed
    [command returned code 255 Thu Jul 03 11:59:26 2014]

    Edit: I uninstalled and tried and older version but got the same problem. I went back to 3.0.1 and it worked.

  3. yenes56

    having exact same issue as Brent. I am using 3.0.2. bitbucket repository was created, pushed from machine A successfully. From machine B, when trying to "incoming" or "pull", I am seeing the abort:authorization. running the -debug showing exactly branch like Brent. Somebody please respond. thank you.

  4. Florian Rubach

    I ran into the same issue with TortoiseHg and windows 7. Solution for me was to change to a password without high ANSI characters (e.g. german umlauts, ÄÖÜ).

  5. Jesse Yowell staff

    This is Jesse from Atlassian Bitbucket. I'm attaching a customer's debug log here, as we can't figure out what is going on:

    Here is the result of the command:
    
    C:\work\LavaBlast>hg push --debug --traceback
    pushing to https://bitbucket.org/repo/repo
    using https://bitbucket.org/repo/repo
    sending capabilities command
    using auth.bb.* for authentication
    bitbucket.org certificate successfully verified
    using auth.bb.* for authentication
    http auth: user ******, password ************
    using auth.bb.* for authentication
    bitbucket.org certificate successfully verified
    query 1; heads
    sending batch command
    using auth.bb.* for authentication
    searching for changes
    all remote heads known locally
    preparing listkeys for "phases"
    sending listkeys command
    using auth.bb.* for authentication
    checking for updated bookmarks
    preparing listkeys for "bookmarks"
    sending listkeys command
    using auth.bb.* for authentication
    sending branchmap command
    using auth.bb.* for authentication
    sending branchmap command
    using auth.bb.* for authentication
    preparing listkeys for "bookmarks"
    sending listkeys command
    using auth.bb.* for authentication
    1 changesets found
    list of changesets:
    76c25843a0ff3e1fb44837493cc7270ff6702be4
    bundling: 1/1 changesets (100.00%)
    bundling: 1/1 manifests (100.00%)
    bundling: FranchiseBlast/App_Data/FranchiseBlast.XML 1/12 files (8.33%)
    bundling: FranchiseBlast/FranchiseBlast.csproj 2/12 files (16.67%)
    bundling: FranchiseBlast/Pages/crmForms.aspx.cs 3/12 files (25.00%)
    bundling: FranchiseBlast/UserControls/Content/SurveyCrm/SurveyCrmEditor.ascx.cs
    4/12 files (33.33%)
    bundling: FranchiseBlast/UserControls/Content/SurveyCrm/SurveyCrmList.ascx 5/12
    files (41.67%)
    bundling: FranchiseBlast/UserControls/Content/SurveyCrm/SurveyCrmList.ascx.cs 6/
    12 files (50.00%)
    bundling: FranchiseBlast/UserControls/Content/SurveyCrm/SurveyCrmList.ascx.desig
    ner.cs 7/12 files (58.33%)
    bundling: FranchiseBlast/Views/Crm/Index.cshtml 8/12 files (66.67%)
    bundling: FranchiseBlast/css/inspinia/style.min.css 9/12 files (75.00%)
    bundling: FranchiseBlast/css/mobile-site.less 10/12 files (83.33%)
    bundling: FranchiseBlast/css/mobile-site.min.css 11/12 files (91.67%)
    bundling: FranchiseBlast/js/controls/SurveyCrm/SurveyCrmEditor.js 12/12 files (1
    00.00%)
    sending unbundle command
    sending 58435 bytes
    using auth.bb.* for authentication
    sending: 57/114 kb (50.00%)
    sending: 57/114 kb (50.00%)
    Traceback (most recent call last):
      File "mercurial\dispatch.pyo", line 140, in _runcatch
      File "mercurial\dispatch.pyo", line 863, in _dispatch
      File "mercurial\dispatch.pyo", line 624, in runcommand
      File "mercurial\dispatch.pyo", line 954, in _runcommand
      File "mercurial\dispatch.pyo", line 925, in checkargs
      File "mercurial\dispatch.pyo", line 860, in <lambda>
      File "mercurial\util.pyo", line 711, in check
      File "mercurial\commands.pyo", line 5115, in push
      File "mercurial\exchange.pyo", line 224, in push
      File "mercurial\exchange.pyo", line 647, in _pushchangeset
      File "mercurial\wireproto.pyo", line 389, in unbundle
      File "mercurial\httppeer.pyo", line 202, in _callpush
      File "mercurial\httppeer.pyo", line 172, in _call
      File "mercurial\httppeer.pyo", line 122, in _callstream
    Abort: authorization failed
    abort: authorization failed
    
  6. Kalle Saunamäki

    I'm also having this same problem (started maybe after 3.3.2 update?), on Windows 7 with Bitbucket as target. Sometimes works after trying to push from command-line (and not from Workbench), sometimes after once logging on to the Bitbucket site. Pulling works, so it isn't about credentials being wrong.

    Here's end of the transaction at the end of it fails:

    ... bundling: 1/2 changesets (50.00%) bundling: 2/2 changesets (100.00%) bundling: 1/1 manifests (100.00%) sending unbundle command sending 2511 bytes using auth.example.* for authentication sending: 2/4 kb (50.00%) sending: 2/4 kb (50.00%) abort: authorization failed

  7. BuildMachine YNAB

    I searched through the Mercurial bug repo, and didn't see this bug logged there yet, so I'm hoping that someone from BitBucket has solved it? I too am getting this error.

    hg push -f --debug --traceback --rev .
    pushing to https://bitbucket.org/ynab/ynabair
    using https://bitbucket.org/ynab/ynabair
    sending capabilities command
    using auth.bb.* for authentication
    bitbucket.org certificate matched fingerprint 45:ad:ae:1a:cf:0e:73:47:06:07:e0:88:f5:cc:10:e5:fa:1c:f7:99
    using auth.bb.* for authentication
    http auth: user buildmachine@youneedabudget.com, password ************
    using auth.bb.* for authentication
    bitbucket.org certificate matched fingerprint 45:ad:ae:1a:cf:0e:73:47:06:07:e0:88:f5:cc:10:e5:fa:1c:f7:99
    query 1; heads
    sending batch command
    using auth.bb.* for authentication
    searching for changes
    all remote heads known locally
    preparing listkeys for "phases"
    sending listkeys command
    using auth.bb.* for authentication
    checking for updated bookmarks
    preparing listkeys for "bookmarks"
    sending listkeys command
    using auth.bb.* for authentication
    1 changesets found
    list of changesets:
    8c4e011e9f0e1c3648eebadba8e027dc1fc87533
    bundling: 1/1 changesets (100.00%)
    bundling: 1/1 manifests (100.00%)
    bundling: YNAB/build/ReleaseNotes.yml 1/1 files (100.00%)
    sending unbundle command
    sending 566 bytes
    using auth.bb.* for authentication
    sending: 0 kb
    sending: 0 kb
    Traceback (most recent call last):
    File "mercurial\dispatch.pyo", line 140, in _runcatch
    File "mercurial\dispatch.pyo", line 863, in _dispatch
    File "mercurial\dispatch.pyo", line 624, in runcommand
    File "mercurial\dispatch.pyo", line 954, in _runcommand
    File "mercurial\dispatch.pyo", line 925, in checkargs
    File "mercurial\dispatch.pyo", line 860, in <lambda>
    File "mercurial\util.pyo", line 711, in check
    File "mercurial\extensions.pyo", line 149, in wrap
    File "mercurial\util.pyo", line 711, in check
    File "hgext\mq.pyo", line 3483, in mqcommand
    File "mercurial\util.pyo", line 711, in check
    File "mercurial\commands.pyo", line 5115, in push
    File "mercurial\exchange.pyo", line 224, in push
    File "mercurial\exchange.pyo", line 647, in _pushchangeset
    File "mercurial\wireproto.pyo", line 389, in unbundle
    File "mercurial\httppeer.pyo", line 202, in _callpush
    File "mercurial\httppeer.pyo", line 172, in _call
    File "mercurial\httppeer.pyo", line 122, in _callstream
    Abort: authorization failed
    abort: authorization failed
    
  8. BuildMachine YNAB

    I am attempting to create a BugZilla account with Selenic so that I can create the bug, but am not having any luck. I agree this isn't a Tortoise issue. I have found another report of this issue on the BitBucket issue tracker, and have posted there: https://bitbucket.org/site/master/issue/11099/push-having-problem-of-authorization

    (I have also written to BitBucket support.)

    So, I suggest we leave the Tortoise folks alone and move our discussion over there. :)

  9. Kaleb Elwert staff

    As far as I know, this has been resolved. Definitely a bitbucket issue. Our new frontends were missing a few key configuration files.

    If you continue to have problems, please feel free to contact us at support@bitbucket.org

  10. ccisystems

    Sorry to bring this up again guys but it seems there's still an issue with PULL now. I get the following messages when trying to pull (albeit quite a large repository - 1.27Gb). Tried many times, the 'got / expected' varies a lot.

    % hg clone --verbose https://*@bitbucket.org/* "C:****" http authorization required for https://bitbucket.org/*** realm: Bitbucket.org HTTP user: *** requesting all changes adding changesets adding manifests adding file changes transaction abort! rollback completed abort: stream ended unexpectedly (got 248033 bytes, expected 281167) [command returned code 255 Wed Mar 25 22:48:42 2015] % hg clone --verbose https://***@bitbucket.org/*** "C:***" http authorization required for https://bitbucket.org/*** realm: Bitbucket.org HTTP user: *** requesting all changes adding changesets adding manifests adding file changes transaction abort! rollback completed abort: stream ended unexpectedly (got 1340807 bytes, expected 3516940) [command returned code 255 Wed Mar 25 23:06:53 2015] % hg clone --uncompressed --verbose https://***@bitbucket.org/*** "C:***" http authorization required for https://bitbucket.org/*** realm: Bitbucket.org HTTP user: ***** streaming all changes 41082 files to transfer, 1.27 GB of data abort: unexpected response from remote server: empty string [command returned code 255 Wed Mar 25 23:23:25 2015]

  11. Log in to comment