# Error for logged in users and Git hang

**URL:** https://meta.discourse.org/t/error-for-logged-in-users-and-git-hang/411513
**Category:** Support
**Created:** [September 2, 2026, 7:08pm UTC](https://meta.discourse.org/t/error-for-logged-in-users-and-git-hang/411513 "2026-09-02T19:08:59Z")
**Posts on this page:** 1
**Showing post:** 11

<div class="post-metadata">

### Author: ![Ed\_S](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ed_s/32/134015_2.png) [@Ed\_S](https://meta.discourse.org/u/Ed_S)
#### Post date: [September 3, 2026, 7:10am UTC](https://meta.discourse.org/t/error-for-logged-in-users-and-git-hang/411513/11 "2026-09-03T07:10:29Z")

</div>

> [@Ed\_S](#):
>
> My forum/logs area is presently showing 4 cases of “pitchfork worker timed out” and it’s not a very busy forum at all.

I’m now seeing 15 cases of pitchfork worker timed out, with two different backtraces. On the linux side pitchfork continues to accrue unreaped children and sometimes I see a git process which is - I think - the culprit.

My change is not a fix and might or might not be helpful. I will revert it.

> [@Ed\_S](#):
>
> I’ve unchecked this feature:
> 
> admin-\>site admin → version checks → clear the checkbox → save

github themselves are [still broken](https://github.com/orgs/community/discussions/206581). The change to HTTP/1.1 for git connections might be a good workaround.

> [@Fatal: could not read Username for 'https://github.com'](https://meta.discourse.org/t/fatal-could-not-read-username-for-https-github-com/411498/5):
>
> It seems to be an issue with Github, found a discussion here

---

_[View the full topic](https://meta.discourse.org/t/error-for-logged-in-users-and-git-hang/411513)._