Mercurial push, abort: authorization failed

Question

I'm having trouble clicking on the mercurial repository:

$ hg push pushing to https://user:***@hg.domain.com/X_repo searching for changes abort: authorization failed 

The same URL (with the same credentials) is accessible through a web browser. Also, I tried this without inserting usr + pass in the url.

HTTPS is configured correctly, I tried both Basic and Digest auth - with no luck.

Pulling (over HTTP) works fine.

I use hgwebdir to service my repo.

What else should I check?

I found this: http://code.google.com/p/support/issues/detail?id=2580 In my case, this is not random, it happens every time.

The relevant part of my vhost conf:

  WSGIScriptAlias / /home/(...)/hgwebdir.wsgi <Directory /home/(...)> AuthType Basic AuthUserFile /(...)/basic-password AuthName (...) Require valid-user Order deny,allow Allow from all </Directory> $ hg -v Mercurial Distributed SCM (version 1.0.2) 

Oddly enough, hg outgoing works fine:

 $ hg outgoing comparing with https://hg.domain.com/X_repo http authorization required realm: ... user: ... password: searching for changes changeset: 64:... tag: tip user: ... date: ... summary: ... 

Answer 1

The problem turned out to be reporter. chown www-data decided ...

Answer 2

If someone wants him to run on the local machine, then adding this to the REPO/.hg/hgrc , do the job:

 [web] allow_push = * push_ssl = false 

as described in this site .

Answer 3

It is strange that you can run hg outgoing but not hg push , as I understand that they both authenticate equally.

Unfortunately, I am not an hgweb expert. Email Mercurial list ([e-mail]) and / or go to IRC ( #mercurial on irc.freenode.net ). There will be many more people to help you there. IRC is especially good because these things are much easier to debug interactively.

Answer 4

For those with TortoiseHg clicking on a web server (another unauthorized user on another PC):

In TortoiseHg: File - Settings - (Either globally or just for the current repository - tabs) then Server settings. Web server

 Push Requires SSL - No Allow Push - * 

This does the same through the user interface as the lukmdo answer above (editing the hgrc file).

Answer 5

Just in case, this may help someone - I ran into this error for unknown reasons, all permissions were ok, and just restarting apache solved it.

Answer 6

This happened to me after changing the password on the bitpack, but although I used SourceTree to manage my password and I changed it to a global one repo, however, my old password, hardcoded in REPO/.hg/hgrc , changed the line and that's it works again

Answer 7

My problem was a little different. Changing the password caused it ... And I had repo/.hgrc and repo/.hg/hgrc . I don’t know why, but this is contradictory.

For recording, the cleanest way I've found is to save the global configuration file (on Windows C:\Users\<user>\mercurial.ini or Linux /home/<user>/.hgrc ) with all the configuration that applies to all to repositories (profiles, plugins / extensions, repositories, etc.) and then behind the repo, just use something like:

 [paths] default = https://path/to/remote/repo # any other repo-specific config 

Why I had another repo-specific mercurial configuration file, I don’t know, now everything is cleaned up and works beautifully.