> From: Eric B <ebenza...@gmail.com>
> [eric git]$ git clone https://e...@git.assembla.com/myproj.git
> Cloning into 'myproj'...
> Password for 'https://e...@git.assembla.com':
> error: RPC failed; result=22, HTTP code = 401
> fatal: The remote end hung up unexpectedly
> In all fairness, I do not know if that is due to my package being installed
> under my home dir vs standard dirs, or if there is a firewall issue/etc,
> but I can confirm that a clone to that repo works properly on another
> system. Similarly, I can confirm that I can d/l data from other https
> sites without issues.
The odds are very good that Git itself is working fine on the
production machine, and that it's able to contact the remote system.
The trouble is that the remote system doesn't like the HTTP request,
probably because it doesn't think your end has authenticated itself
correctly. A less-likely cause would be that Git isn't making the
request "properly", and a web proxy (or elaborate firewall) is
intercepting the request and denying it.
Can you manually make the same HTTP request work? "wget" is a good
tool for that. Of course, you have to find out what URL is actually
being fetched, although a fetch of "/" will get you some information.
If you use an http: URL for the repository and snoop the network
traffic, you can find the URL used in the HTTP request. (You can do
that on your development system.) Or get it with GIT_CURL_VERBOSE=1,
as Konstantin suggests.