Remote: HTTP Basic: Access denied since last update

GitLab CI/CD
1

Problem to solve

Since the last update I am suddenly getting Access denied on 1 host trying to pull from a private gitlab instance with basic authentication.
Nothing can be cloned or pulled on this one host.
The credentials work just fine on another host so it’s not a typo in the password.
Trying to clone a repo to a new location also fails.

I’m assuming somehow the ip is blocked somewhere, i need to know why, how to fix it and how to prevent it. There is nothing obvious in any of the auth_ logs, they are all empty.

Steps to reproduce

git pull / clone any repo on host 1 via http with built-in credentials fails
git pull / clone same repo’s that failed on host 1 but on host 2 via http with built-in credentials works

Configuration

There is no non default configuration besides the mail server,port 80 redirect and local storage location.

Versions

17.5.2-ee

  • Self-managed
  • Dedicated
  • Self-hosted Runners (They’re installed but unused)

Versions
System information
System:
Current User: git
Ruby Version: 3.2.5
Gem Version: 3.5.17
Bundler Version:2.5.11
Rake Version: 13.0.6
Redis Version: 7.0.15
Sidekiq Version:7.2.4
Go Version: unknown

GitLab information
Version: 17.5.2-ee
Revision: 9811944b476
Directory: /opt/gitlab/embedded/service/gitlab-rails
DB Adapter: PostgreSQL
DB Version: 14.11
GitLab Shell
Version: 14.39.0
Gitaly

  • default Version: 17.5.2
  • default Git Version: 2.46.2
1 Like
2

Just as a little update, the host is headless so I installed lynx and tried the accessing via web.
Trying to log in via web from the broken host gives a invalid user or password.
This works from a different host with the same credentials.

So I set up an ssh-key and added an alt connection, and that works. So I have a temporary workaround but for reasons I need the authentication via https to also work.
There has to be some weird reason for http auth to be failing from just this one host.