What can I do if when I push files to server it tells me that my repository is possibly corrupt?

[Maxklii]

I was trying to push files to my server, but a pop up appeared and it said:

“fatal protocol error: bad line length character: |Pa”

“FATAL ERROR: error reading from console: error 109”

After some trials, I managed to push it without errors. I have been following a setup guide during the process, so after I pushed the files I had to run the command “$ git pull hub main” but it rejected me saying that the repository was possibly corrupt. I checked that everything was ok and even cloned the files again, so I don’t know how to solve this. I was told to download an older version of sourcetree, but is that the only option?

[Carlos Garcia Navarro · Accepted solution]

Hi @Maxklii ,

Welcome to the Community!  When you said that you made it work after some trials, what did you change to make it work?

Hmm... yeah, it seems that using an older version has fixed it for others in the past:

https://stackoverflow.com/questions/76709045/sourcetree-newer-than-3-4-7-cant-fetch-pull-with-a-fatal-protocol-error-bad-li

[Maxklii]

To be honest i didn't do anything, i just kept insisting until it worked. I will consider to switch versions tho... thanks for the welcome!

[Carlos Garcia Navarro]

Ok... Sorry about that! I've requested help from Atlassian Support to see if they can take a look!

[Earl McCutcheon]

Hello,  

I saw the ask for help from Carlos and I am Hopping in with a little more context but I do not really have too much more to offer beyond what  @Carlos Garcia Navarro already mentioned.

Overall this is a fairly standard message/warning that you should expect when there is any kind of connection error from not having connected to the remote device before or token expatriation or simply passing incorrect authentication credentials during this portion of the call.

And I located a similar but different stack overflow post with related behavior (all be it to different affected products) covering this error viewable HERE noting the final resolution that was mentioned was a re-install of the erring extension, so back to the initial suggestion installing a different version or simply uninstall and re-installing the current version would be a great starting point to try and clear this out.

Regards,
Earl