Problem solved.
Windows: Before connecting Bitbucket (AKA stash) you need to clean all proxies from both Git and console environment:
SET HTTP_PROXY=
SET HTTPS_PROXY=
git config --global --unset http.proxy
git config --global --unset https.proxy
git clone http://yourUser@stashAddress:stashPort/apptest.git
But if you need to connect to public repositories like github, then it's necessary to define proxies again:
SET HTTP_PROXY=proxyaddress:port
SET HTTPS_PROXY=proxyaddress:port
git config --global http.proxy http://proxyaddress:port
git config --global https.proxy http://proxyaddress:port
I think it may be useful for other developers working behind corporate firewalls.
Linux
unset HTTP_PROXY
unset HTTPS_PROXY
git config --global --unset http.proxy
git config --global --unset https.proxy
git clone http://yourUser@stashAddress:stashPort/apptest.git
To define proxies again:
export HTTP_PROXY=proxyaddress:port
export HTTPS_PROXY=proxyaddress:port
git config --global http.proxy http://proxyaddress:port
git config --global https.proxy http://proxyaddress:port
Take care with uppercase of environment variables. Some OS versions may need lowercase or may have defined lowercase variables by default.