most of the time i get a fatal protocol error when pushing/ pulling from my remote repo. its an older windows 10 (after being updated) lenovo machine. when i switch my wifi connection to use my mobile hotspot (verizon) , it works fine. i am on a team of ten and am the only one who has this issue.
the error is:
fatal: protocol error: bad line length character: <html' (TRUNCATED
fatal: the remote end hung up unexpectedly
error: RPC failed; HTTP 302 curl 22 the requested URL returned error: 302
Hi
It looks like you might be getting a HTML page back rather than the expected response, the fact that it is a 302 suggest some form of redirect.
Do you have any proxy settings on you machine or on your network? That might explain the different behavior between the two networks.
When I go to Settings > Network Proxy > Manual Proxy Setup, I can see that I am not using a proxy server - is that what you are asking about?
It is not the wifi network that I am using, as the rest of my team does not have this problem.
Any other ideas?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any chance you could tell me how to do that on a Windows 10 machine?
I'm assuming this is different from the 'Settings > Network Proxy > Manual Proxy Setup' I mentioned above.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This has some pointers https://www.digitalcitizen.life/how-set-proxy-server-windows-10
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That looks like exactly what I described above. (Settings > Network Proxy > Manual Proxy Setup)
According to that, I am not using a proxy. Are there any other reasons it wouldn't work as intended?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, not that I can think of. The 302 error you are seeing suggests something is in the middle, a proxy or firewall, causing a redirect. But its not obvious from there error above what is causing it.
If it all works when you switch networks to your hotspot it very strongly suggests it is network related not Sourcetree directly.
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.