Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Bitbucket Server: The requested URL returned error: 403

Daniel Karoll
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
August 23, 2018

I have installed a fresh copy of Bitbucket Server v5.13.0 on a local domain server, and I'm able to create projects and repositories through the web browser without issues. When I try to clone my empty repository using git CMD or BASH I get this error: 

Cloning into 'testrepo' ... 

fatal: unable to access 'http://172.16.1.163:7990/scm/tp/testrepo.git/': The requested URL returned error: 403

I believe 403 should point to an access level issue, but i've created this repo with the administrator account, making sure it had full privileges to the repo and that the git config information was correct. 

bitbucketwtf.PNG

 

I've also tried to clone in sourcetree using the 'clone in sourcetree' link with the same results. The odd part is in sourcetree under 'remote repositories' I can see 'testrepo' on the repository list, i just cant clone from it...

sourcetreewtf.PNG.I'm not using SSH

 

2 answers

2 votes
Lumpenstein
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 13, 2018

Figured out a solution ? Having the same problem atm :/

0 votes
Daniel Karoll
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 13, 2018

After setting up SSH, everything worked properly:

https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html

I found that in my organization some users can connect using http right out of the box and others need to use SSH. I'm not sure why this occurs but it seems to always work over SSH. 

Lumpenstein
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 13, 2018

Thanks for answering ! Figured out the problem on my side as well, the bank I'm currently working in hass some proxy servers that were blocking the connection (figured it out by adding verbose logging to the git commands), needed to set 'git config remotes.MYREMOTE.proxy "" ' to bypass the proxy. 

I think you had the same problem, since using ssh bypasses the proxy ass well.

More info in this SO:


https://stackoverflow.com/questions/16538372/git-proxy-bypass

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events