Can't clone Bitbucket repo via https on Debian. I always get error:
abort: authorization failed
Mercurial Distributed SCM (version 1.4.1), Python 2.5.2
Thru ssh and http(w/o pass) work fine.
After updating my own password on Bitbucket all works fine
Related
Recently I installed in a Fiware instance STH-Comet through the command:
git clone https://github.com/telefonicaid/fiware-sth-comet.git
cd fiware-sth-comet
npm install
Today I went to install again and when cloning the STH-Comet repository the following error arose:
Initialized empty Git repository in /etc/fiware-sth-comet/.git/
error: while accessing https://github.com/telefonicaid/fiware-sth-comet.git/info/refs
fatal: HTTP request failed**
Have there been any changes to the STH-Comet repository?
Maybe, it is due a permission denied. Try to set up your public key on github. Instructions here: https://help.github.com/articles/generating-ssh-keys/ and check it again. There were no changes in that repository.
I've installed reviewboard (both in windows and linux), I successfully added an svn repository (i see the commits on the repo in http://reviewboard.ourcompany.com/reviewboard/r/new/) but I can't figure out how to properly add a mercurial repo, I added it to the repo list but there i no way of getting the commits out of it.
I tried using as path:
1)the http address of the mercurial server (the address is correct)
2)cloning locally a bare repo from the http server
I couldn't find any tutorial on how to configure reviewboard with mercurial
I have the all-in-one download with TortoiseHg 2.6.1 and Mercurial 2.4.1 installed on windows server 2k8. I created a repository, served it on port 8000. There are no mercurial configuration files setup right now for this repository. No global config files either. When I try to clone this repos through eclipse (MercruialEclipse plugin) from a remote computer over the internet, I get:
abort: HTTP Error 404: Not Found
What does this mean?
Thanks.
Found the solution. The command syntax was incorrect. The incorrect syntax I was using was
hg clone http://www.xyz.com:8000/<dirname for the repo clone>
The correct command is:
hg clone http://www.xyz.com:8000/ <dirname for the repo clone>
Should also mention that I am using version 2.3.2(mercurial)
I am planning to use mercurial for a new project but I'm having some problem accessing the bitbucket repository. I'm new to mercurial, but I have used git previously.
I get the following error when peforing a hg clone or push:
abort: error: An existing connection was forcibly closed by the remote host
I only have this problem when using my work pc, when accessing the repository from my home pc I can clone and push just fine, any ideas, is there some firewall setting that needs to be configured?
I'm using Mercurial-2.1.2-x64 on windows 7 x64 for both pcs.
So I found the source of the error, I had initially installed tortoise hg which had created the following mercurial.ini file in my user directory, once I deleted this file, it resolved the issue. I suppose the problem was that I had specified the repository url instead of an actual http proxy...
# Generated by TortoiseHg settings dialog
[tortoisehg]
cipushafter =
[http_proxy]
host = https://****#bitbucket.org/****/*** (my repository path)
Browse to the project folder in command prompt and run hg rollback.
Windows XP, Mercurial 1.6.4
hg clone https://demas#bitbucket.org/demas/start.here
destination directory: start.here
requesting all changes
abort: error:
But if I use SSH all works fine
hg clone ssh://hg#bitbucket.org/demas/start.here
Debug info:
hg clone --debug https://demas#bitbucket.org/demas/start.here
using https://bitbucket.org/demas/start.here
http auth: user demas, password not set
sending between command
destination directory: start.here
sending heads command
requesting all changes
sending changegroup command
abort: error:
Why? And how I fix it?
Use a custom configuration to workaround the handling of self-signed certificates:
Note that per the default settings installed, connect to repositories with self-signed certificates fail with 1.7.3. You need to adjust the default configuration for that case.
References
CA Certificates in hg on Windows
hg import from a https URL fails