GitLab Runner Not Picking Up Jobs

Share
Ongoing Linux, macOS, Windows, Docker, Kubernetes Updated November 13, 2026Based on 4 user reportsHow we research

Quick answer

If the runner shows online but never starts jobs, the cause is nearly always tags, run-untagged, protected or locked settings, or a runner process that is not polling correctly.

Most likely fix: Verify the runner process

How to fix it

Try these in order — the most common fix is first.

  1. 1. Verify the runner process

    1. Run sudo gitlab-runner verify to confirm it can reach GitLab and the token is valid.
    2. Check logs: journalctl --unit=gitlab-runner.service -n 100 --no-pager (or docker logs / kubectl logs).
    3. Restart: sudo systemctl restart gitlab-runner.service.
    Did this fix it?
  2. 2. Turn on debug logging

    1. Set log_level = "debug" at the top of /etc/gitlab-runner/config.toml and restart.
    2. Remove it afterwards because debug logs can expose secrets.
    Did this fix it?
  3. 3. Fix tag and scope settings

    1. In Settings > CI/CD > Runners edit the runner: enable "Run untagged jobs" or add the job tags.
    2. Untick Protected if the branch is not protected.
    Did this fix it?
  4. 4. Fix certificate and DNS errors

    1. For "x509: certificate signed by unknown authority" add your CA certificate to the runner per the self-signed certificates docs.
    2. If containers cannot reach GitLab but the host can, set dns = ["<ip>"] under [runners.docker] in config.toml.
    Did this fix it?
  5. 5. Keep versions aligned and avoid duplicates

    1. Upgrade gitlab-runner to match your GitLab major.minor version.
    2. Never run multiple runner instances on the same config.toml.
    Did this fix it?

Symptoms

Runner appears in the list (or as offline) but jobs stay pending, or gitlab-runner logs show errors contacting GitLab.

Why it happens

  • Tag mismatch or runner not allowed to run untagged jobs
  • Protected or locked runner scope
  • Runner service not running or two runner instances sharing one config.toml
  • Certificate (x509) or DNS problems reaching GitLab from the runner or its containers
  • Runner and GitLab versions out of sync
  • Long polling issues delaying job start

This guide also covers

  • gitlab runner not picking up jobs
  • gitlab runner offline
  • gitlab-runner not running jobs
  • gitlab runner x509 certificate signed by unknown authority

Still not working?

If GitLab keeps failing, you're not alone. See every GitLab problem users report or the alternatives people switch to.

Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.

Talk to us
Fixed it? Share this guide

Other GitLab errors

All 11 GitLab errors and fixes →