Troubleshooting GitLab Duo
When working with GitLab Duo, you might encounter issues.
Start by running a health check to determine if your instance meets the requirements to use GitLab Duo.
If the health check does not resolve your problem, review these troubleshooting steps.
GitLab Duo features do not work on self-managed
In addition to ensuring GitLab Duo features are turned on, you can also do the following:
As administrator, run a health check for GitLab Duo.
In GitLab 17.5 and later, you can use the UI to run health checks and download a detailed report that helps identify and troubleshoot issues.
In GitLab 17.4, you can run the health check Rake task to generate a detailed report that helps identify and troubleshoot issues.
sudo gitlab-rails 'cloud_connector:health_check(root,report.json)'
In GitLab 17.3 and earlier, you can download and run the
health_check
script to generate a detailed report that helps identify and troubleshoot issues.Download the health check script:
wget https://gitlab.com/gitlab-org/gitlab/-/snippets/3734617/raw/main/health_check.rb
Run the script using Rails Runner:
gitlab-rails runner [full_path/to/health_check.rb] --debug --username [username] --output-file [report.txt]
Usage: gitlab-rails runner full_path/to/health_check.rb --debug Enable debug mode --output-file FILE Write a report to FILE --username USERNAME Provide a username to test seat assignments --skip [CHECK] Skip specific check (options: access_data, token, license, host, features, end_to_end)
Verify that the GitLab instance can reach the required GitLab.com endpoints. You can use command-line tools such as
curl
to verify the connectivity.curl --verbose "https://cloud.gitlab.com" curl --verbose "https://customers.gitlab.com"
If an HTTP/S proxy is configured for the GitLab instance, include the
proxy
parameter in thecurl
command.# https proxy for curl curl --verbose --proxy "http://USERNAME:PASSWORD@example.com:8080" "https://cloud.gitlab.com" curl --verbose --proxy "http://USERNAME:PASSWORD@example.com:8080" "https://customers.gitlab.com"
Optional. If you are using a proxy server between the GitLab application and the public internet, disable DNS rebinding protection.
Manually synchronize subscription data.
- Verify that the GitLab instance synchronizes your subscription data with GitLab.
GitLab Duo features not available for users
In addition to turning on GitLab Duo features, you can also do the following:
- Verify that subscription seats have been purchased.
- Ensure that seats are assigned to users.
- For IDE users with the GitLab Duo extension:
- Verify that the extension is up-to-date.
- Run extension setting health checks, and test the authentication.
Docs
Edit this page to fix an error or add an improvement in a merge request.
Create an issue to suggest an improvement to this page.
Product
Create an issue if there's something you don't like about this feature.
Propose functionality by submitting a feature request.
Feature availability and product trials
View pricing to see all GitLab tiers and features, or to upgrade.
Try GitLab for free with access to all features for 30 days.
Get help
If you didn't find what you were looking for, search the docs.
If you want help with something specific and could use community support, post on the GitLab forum.
For problems setting up or using this feature (depending on your GitLab subscription).
Request support