I am having issues accessing a repository on gitlab. The issue seems related to the usage of Git LFS. I cannot fetch, pull or push without getting an error 403 or an authorization error.
Also, cloning seems to not work consistently, I sometimes get an error 403 when I try to clone any repository from gitlab. The issues started since yesterday. I have tried to do a clean install of SourceTree but the issue is still present.
I have also tried to clone and perform operations on the repositories of my team on gitlab through other git clients (i.e. GitHub Client and GitKraken) and everything seem to work fine, so I suppose it's something related to how SourceTree is configured.
Command: git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks ls-remote https://gitlab.com/team/test.git
Output:
Error: fatal: unable to access 'https://gitlab.com/team/test.git/': The requested URL returned error: 403
----------------------------------------------------------------------------------------
git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks push -v --tags origin master:master
fatal: unable to access 'https://gitlab.com/team/test.git/': The requested URL returned error: 403
Pushing to https://gitlab.com/team/test.git
Completed with errors, see above.git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks push -v --tags origin master:master
fatal: unable to access 'https://gitlab.com/team/test.git/': The requested URL returned error: 403
Pushing to https://gitlab.com/team/test.git
Completed with errors, see above.
----------------------------------------------------------------------------------------
git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks fetch --no-tags origin
fatal: unable to access 'https://gitlab.com/team/test.git/': The requested URL returned error: 403
Completed with errors, see above.
This error means that gitlab is not recognising your login/credentials/certificates.
In turn, that means you've probably not given the right details to Sourcetree.
Ok, so there's a network problem between your first machine and the git server, or the git server is configured to refuse you access.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am sure, you've got two computers that can connect and log in, and a third that can not. The problem has to be something different in that third computer. If it's similarly configured to the other two, then it has to be the network. If it is completely different, then its network settings are a problem.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
First of all, thank you very much for your patience. Anyway, I didn't specify that github desktop is installed on the same machine where sourcetree is refusing to work. Do you think the problem is still network related?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yep, "same machine" is great for debugging, it rules out so... many... things, but not quite the network.
Sourectree is going out over standard routes and ports, so the question now becomes "what is github desktop doing differently?")
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.