Importing from Self-Hosted GitLab
Prerequisites
- Access to a self-hosted GitLab instance (version 14.0 or later recommended)
- Admin access to that GitLab instance to register an OAuth application or a Personal Access Token for your account
Option A — OAuth (Recommended)
Step 1 — Register an OAuth App on Your GitLab Instance
- On your self-hosted GitLab, go to User Settings → Applications (or Admin Area → Applications for an instance-wide app)
-
Fill in:
- Name: GitBlixt
-
Redirect URI:
https://git.yourdomain.com/oauth/gitlab_self_hosted/callback -
Scopes:
read_user,read_api,read_repository
- Save and copy the Application ID and Secret
-
Set these on your GitBlixt instance:
Restart the container.GITLAB_SH_CLIENT_ID=your-application-id GITLAB_SH_CLIENT_SECRET=your-secret
Step 2 — Connect
- Go to Dashboard → Import Repository
- Select Self-Hosted GitLab
- Enter your GitLab instance URL (e.g.
gitlab.yourcompany.com) - Click Connect — you'll be redirected to your GitLab instance to authorize
- After authorizing, your projects will be listed
Step 3 — Import
Select your projects and click Import Selected. Progress is shown in real time.
Option B — Personal Access Token
If you can't register an OAuth application, you can import using a Personal Access Token.
- On your self-hosted GitLab, go to User Settings → Access Tokens
-
Create a token with the following scopes:
read_user,read_api,read_repository - Copy the token
- In GitBlixt, go to Import → Self-Hosted GitLab → Use token instead
- Enter your GitLab instance URL and paste your token
Network Accessibility
GitBlixt needs to be able to reach your self-hosted GitLab instance over HTTP/HTTPS to clone repositories and call its API. If your GitLab is on a private network, make sure your GitBlixt server can reach it (VPN, peering, etc.).
Self-Signed Certificates
If your self-hosted GitLab uses a self-signed certificate, you'll need to add that certificate to GitBlixt's trust store. Contact your administrator or see the Troubleshooting page.