Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #6239

Closed
Open
Created Feb 04, 2014 by Administrator@rootOwner

503 Error on GitLab CI HTTP token-based access to GitLab

Created by: jtreml

I've just upgrade installations of both GitLab and GitLab CI to the latest versions (6.4.x to 6.5.1 and 4.1.x to 4.2.2) and GitLab CI now gives the following error when trying to access GitLab to run a build:

error: The requested URL returned error: 503 while accessing http://gitlab-ci-token:XXXXXXXXXXXXXXXXXXXXX@gitlab/group1/project1.git/info/refs
fatal: HTTP request failed

This happens with ALL projects, projects that have been working flawlessly for months before the upgrade. I've double-checked all the settings, tokens, everything and couldn't track down the issue. None of the checks show anything unusual either.

Not sure if this helps, but when trying the above URL (with valid token) in a web browser it brings up the browser's native authentication dialog asking for username and password.

Any idea what might be causing this problem?

Assignee
Assign to
Time tracking