<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=17034) </details> <!--IssueSummary end--> Zendesk: https://gitlab.zendesk.com/agent/tickets/45523 When a user account is blocked and a user pushed using Git over SSH, we display a useful error message: `GitLab: Your account has been blocked.`. However, when using Git over HTTP, we give a standard (if not cryptic) `remote: Not Found`. I completely understand why we give a 404 - not wanting to leak information. Failing HTTP auth is a little different than using Git over SSH, where you're already 'authenticated' using your SSH key but are then not authorized because the account is blocked. I wonder if there's any way we can send back a nicer error message for Git over HTTP in some way. cc/ @jacobvosmaer-gitlab @DouweM @ayufan You are the few lucky ones that may have worked in this area of code. What do you think?