How to catch a glitch with git push?

Question

git

It works absolutely fine from the repository git pull, but I can only send 3-4 files in a commit, otherwise the commit simply does not go away. It looks like this

$ git push origin branch_name
Подсчет объектов: 11, готово.
Delta compression using up to 8 threads.
Сжатие объектов: 100% (11/11), готово.
Запись объектов: 100% (11/11), 1.40 KiB | 0 bytes/s, готово.
Total 11 (delta 9), reused 0 (delta 0)

After this appeared in the console, nothing else happens even after a lot of time and there is no new branch in the repository. This is if five or more files are changed in a commit, it goes away in small batches.
Tried

echo 'ssh -vvv $*' > ssh && chmod +x ssh
GIT_SSH="$PWD/ssh" git pull origin master

I start GIT_SSH="$PWD/ssh" git push origin branch_name
I see a lot of information, but all this, in principle, is no different from a regular push up to this point

Подсчет объектов: 18, готово.
Delta compression using up to 8 threads.
Сжатие объектов: 100% (18/18), готово.
Запись объектов: 100% (18/18), 3.16 KiB | 0 bytes/s, готово.
Total 18 (delta 6), reused 0 (delta 0)
debug2: channel 0: read<=0 rfd 5 len 0
debug2: channel 0: read failed
debug2: channel 0: close_read
debug2: channel 0: input open -> drain
debug2: channel 0: ibuf empty
debug2: channel 0: send eof
debug3: send packet: type 96
debug2: channel 0: input drain -> closed

As a matter of fact, in a normal push, after debug2: channel 0: input drain -> closedthe process goes further, remote etc, and here it just stops and there is no hint of a reason.
GIT_TRACE=1 git push originalso showed no deviations at all, until the Total 11 (delta 9), reused 0 (delta 0)process goes on, and then stops, I have to stop after ^C.

Answer 1

Well, over time, the problem disappeared.

Answer 2

It's most likely a communication problem.
Try checking with https://confluence.atlassian.com/bbkb/troubleshoot...