Hacktoberfest 2026 : les issues que les mainteneurs ont marquées pour octobre, ouvertes et accessibles aux débutants. Parcourir les issues Hacktoberfest

Unable to clone self-hosted private GitLab repos via token

Ouverte
#206 1 commentaire 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
3/5
Temps estimé
1-2 jours
Accessibilité débutants
35/100
Type d'issue
Bug
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
git, typescript
Domaine
devops

Piste de recherche

Start by tracing the GitLab repository discovery and cloning path, using the configuration and simple-git error output as entry points. Reproduce the self-hosted private repository case and verify the clone URL and token handling; done means repositories clone successfully over the intended protocol without authentication failures.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

This may just be a configuration issue, but I'm having problems getting SourceBot to pull a self-hosted, private repository via a token. Here's my config:

{
    "$schema": "https://raw.githubusercontent.com/sourcebot-dev/sourcebot/main/schemas/v2/index.json",
    "repos": [
        {
            "type": "gitlab",
            "url": "https://gitlab.SOME_HOST.com",
            "token": "SOME_TOKEN",
            "groups": [ "SOME_GROUP" ],
            "exclude": {
                "archived": true,
                "repos": [
                    "SOME_PATH/**",
                    "SOME_OTHER_PATH",
                    "A_THIRD_PATH"
                ]
            }
        }
    ]
}

And here's the log output:

[Info] Sourcebot version: v2.8.2
[Info] Disabling telemetry since SOURCEBOT_TELEMETRY_DISABLED was set.
[Info] Using config file at: '/data/sourcebot-config.json'.
2025-02-21 19:50:38,667 CRIT Supervisor is running as root.  Privileges were not dropped because no user is specified in the config file.  If you intend to run as root, you can set user=root in the config file to avoid this message.
2025-02-21 19:50:38,671 INFO supervisord started with pid 7
2025-02-21 19:50:39,674 INFO spawned: 'backend' with pid 390
2025-02-21 19:50:39,677 INFO spawned: 'web' with pid 391
2025-02-21 19:50:39,680 INFO spawned: 'zoekt' with pid 394
[web] |   ▲ Next.js 14.2.21
[web] |   - Local:        http://localhost:3000
[web] |   - Network:      http://0.0.0.0:3000
[web] |
[web] |  ✓ Starting...
[web] |  ✓ Ready in 121ms
[backend] | 2025-02-21T19:50:40.424Z info: [main] Syncing configuration file /data/sourcebot-config.json ...
[backend] | 2025-02-21T19:50:40.490Z debug: [GitLab] Fetching project info for group SOME_GROUP...
2025-02-21 19:50:41,492 INFO success: backend entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-21 19:50:41,492 INFO success: web entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
2025-02-21 19:50:41,492 INFO success: zoekt entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
[backend] | 2025-02-21T19:50:42.387Z debug: [GitLab] Found 29 projects in group SOME_GROUP in 1897ms.
[backend] | 2025-02-21T19:50:42.389Z debug: [GitLab] Found 29 total repositories.
[backend] | 2025-02-21T19:50:42.417Z info: [main] Discovered 29 unique repositories from config.
[backend] | 2025-02-21T19:50:42.447Z info: [main] Synced configuration file /data/sourcebot-config.json in 2.017s
[backend] | 2025-02-21T19:50:42.448Z info: [main] Cloning gitlab.SOME_HOST.com/SOME_GROUP/SOME_REPO...
[backend] | 2025-02-21T19:50:42.586Z error: [main] Cloning into bare repository '/data/.sourcebot/repos/gitlab.SOME_HOST.com/SOME_GROUP/SOME_REPO.git'...
[backend] | remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password. If a token was provided, it was either incorrect, expired, or improperly scoped. See http://gitlab.SOME_HOST.com/help/topics/git/troubleshooting_git.md#error-on-git-fetch-http-basic-access-denied
[backend] | fatal: Authentication failed for 'http://gitlab.SOME_HOST.com/SOME_GROUP/SOME_REPO.git/'
[backend] |
[backend] | Error: Cloning into bare repository '/data/.sourcebot/repos/gitlab.SOME_HOST.com/SOME_GROUP/SOME_REPO.git'...
[backend] | remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password. If a token was provided, it was either incorrect, expired, or improperly scoped. See http://gitlab.SOME_HOST.com/help/topics/git/troubleshooting_git.md#error-on-git-fetch-http-basic-access-denied
[backend] | fatal: Authentication failed for 'http://gitlab.SOME_HOST.com/SOME_GROUP/SOME_REPO.git/'
[backend] |
[backend] |     at Object.action (file:///app/node_modules/simple-git/dist/esm/index.js:4462:25)
[backend] |     at PluginStore.exec (file:///app/node_modules/simple-git/dist/esm/index.js:4501:25)
[backend] |     at file:///app/node_modules/simple-git/dist/esm/index.js:1369:43
[backend] |     at new Promise (<anonymous>)
[backend] |     at GitExecutorChain.handleTaskData (file:///app/node_modules/simple-git/dist/esm/index.js:1367:16)
[backend] |     at GitExecutorChain.<anonymous> (file:///app/node_modules/simple-git/dist/esm/index.js:1351:44)
[backend] |     at Generator.next (<anonymous>)
[backend] |     at fulfilled (file:///app/node_modules/simple-git/dist/esm/index.js:45:24)
[backend] |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[backend] | 2025-02-21T19:50:42.588Z info: [main] Cloning gitlab.SOME_HOST.com/SOME_GROUP/SOME_OTHER_REPO...
[backend] | 2025-02-21T19:50:42.671Z error: [main] Cloning into bare repository '/data/.sourcebot/repos/gitlab.SOME_HOST.com/SOME_GROUP/SOME_OTHER_REPO.git'...
[backend] | remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password. If a token was provided, it was either incorrect, expired, or improperly scoped. See http://gitlab.SOME_HOST.com/help/topics/git/troubleshooting_git.md#error-on-git-fetch-http-basic-access-denied
[backend] | fatal: Authentication failed for 'http://gitlab.SOME_HOST.com/SOME_GROUP/SOME_OTHER_REPO.git/'
[backend] |
[backend] | Error: Cloning into bare repository '/data/.sourcebot/repos/gitlab.SOME_HOST.com/SOME_GROUP/SOME_OTHER_REPO.git'...
[backend] | remote: HTTP Basic: Access denied. If a password was provided for Git authentication, the password was incorrect or you're required to use a token instead of a password. If a token was provided, it was either incorrect, expired, or improperly scoped. See http://gitlab.SOME_HOST.com/help/topics/git/troubleshooting_git.md#error-on-git-fetch-http-basic-access-denied
[backend] | fatal: Authentication failed for 'http://gitlab.SOME_HOST.com/SOME_GROUP/SOME_OTHER_REPO.git/'
[backend] |
[backend] |     at Object.action (file:///app/node_modules/simple-git/dist/esm/index.js:4462:25)
[backend] |     at PluginStore.exec (file:///app/node_modules/simple-git/dist/esm/index.js:4501:25)
[backend] |     at file:///app/node_modules/simple-git/dist/esm/index.js:1369:43
[backend] |     at new Promise (<anonymous>)
[backend] |     at GitExecutorChain.handleTaskData (file:///app/node_modules/simple-git/dist/esm/index.js:1367:16)
[backend] |     at GitExecutorChain.<anonymous> (file:///app/node_modules/simple-git/dist/esm/index.js:1351:44)
[backend] |     at Generator.next (<anonymous>)
[backend] |     at fulfilled (file:///app/node_modules/simple-git/dist/esm/index.js:45:24)
[backend] |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
(etc. -- continues for all remaining repos in the GitLab group)

Based on some quick testing on the command line, it appears this is due to SourceBot using HTTP instead of HTTPS when trying to clone the repositories. Is there a way to switch the "git clone" to use HTTPS?

Langage dominant
TypeScript
Étoiles
3.9k
Forks
374
Merge moyen
21 h 18 min
PR mergées (30 j)
39

Guide de contribution

Ouvrir le guide de contribution

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de sourcebot-dev/sourcebot

Toutes les issues de sourcebot-dev/sourcebot

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.