After upgrading our self-managed GitLab instance to 18.0, our CI/CD pipelines started failing when trying to clone or fetch the repository via HTTP. Prior to the upgrade everything worked without the need for deploy tokens or SSH setup.
What we’re seeing:
remote: HTTP Basic: Access denied.
fatal: Authentication failed for 'http://git.playcraftex.net/group/project.git/'
What we expected:
GitLab Runner should automatically be able to fetch the repository using the built-in CI_JOB_TOKEN
, just like it did before.
We’ve reviewed the following:
- Tried everything what Google and ChatGPT offered
- GitLab docs about
CI_JOB_TOKEN
- Forum threads and MR !185987
- GitLab issue #536833
Configuration
.gitlab-ci.yml
:
stages:
- test
- deploy
test:
stage: test
script:
- ./gradlew clean test --info --stacktrace
deploy-master:
stage: deploy
script:
- rsync -avz --delete ./deploy/*.jar /home/minecraft/plugins/
only:
- mainssssss
deploy-develop:
stage: deploy
script:
- rsync -avz --delete ./deploy/*.jar /var/lib/pterodactyl/volumes/aab5f19d-4ebb-47ec-89e8-0a42de4ac6fa
only:
- develop
Runner: Shell executor
GitLab: HTTP only, no SSH used
Repo is private
Versions
GitLab version:
GitLab-ce: 18.0.0
Runner version:
gitlab-runner 18.0.2 (4d7093e1)
Let us know if we missed anything obvious. Or how we can fix this Problem. because I have no Idea.
Thank you!