Hacktoberfest 2026: die Issues, die Maintainer für den Oktober markiert haben – offen und einsteigerfreundlich. Hacktoberfest-Issues durchsuchen

Certificate error

Offen
#100 7 Kommentare 1 Reaktion 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
35/100
Issue-Typ
Bug
Klarheit
Muss geklärt werden
Aktivitätsstatus
Veraltet
Tech-Stack
docker, gitlab, node.js, typescript

Rechercherichtung

Start with the Docker startup path shown in the stack trace, especially packages/backend/dist/main.js, gitlab.js, and utils.js, and trace the @gitbeaker/rest request. Reproduce the self-hosted GitLab certificate failure, then define and verify the supported certificate injection or bypass behavior for the container.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

bug

Hi, I'm trying to use sourcebot for indexing a self-hosted instance.
When I start the docker image it immediately stop with this error:

[backend] | 2024-11-29T13:13:42.246Z debug: [GitLab] Fetching all projects visible in https://gitlab.*****.com....
[backend] | 2024-11-29T13:13:42.349Z error: [main] Failed to sync configuration file /data/config.json with error:
[backend] | TypeError: fetch failed
[backend] |     at node:internal/deps/undici/undici:13392:13
[backend] |     at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
[backend] |     at async defaultRequestHandler (file:///app/node_modules/@gitbeaker/rest/dist/index.mjs:66:22)
[backend] |     at async file:///app/node_modules/@gitbeaker/core/dist/index.mjs:99:22
[backend] |     at async measure (file:///app/packages/backend/dist/utils.js:5:18)
[backend] |     at async getGitLabReposFromConfig (file:///app/packages/backend/dist/gitlab.js:23:53)
[backend] |     at async syncConfig (file:///app/packages/backend/dist/main.js:109:37)
[backend] |     at async measure (file:///app/packages/backend/dist/utils.js:5:18)
[backend] |     at async _syncConfig (file:///app/packages/backend/dist/main.js:191:36)
[backend] |     at async main (file:///app/packages/backend/dist/main.js:226:5) {
[backend] |   [cause]: Error: unable to verify the first certificate
[backend] |       at TLSSocket.onConnectSecure (node:_tls_wrap:1677:34)
[backend] |       at TLSSocket.emit (node:events:518:28)
[backend] |       at TLSSocket._finishInit (node:_tls_wrap:1076:8)
[backend] |       at ssl.onhandshakedone (node:_tls_wrap:862:12) {
[backend] |     code: 'UNABLE_TO_VERIFY_LEAF_SIGNATURE'
[backend] |   }

while debug is active, it's not very clear to me which certificate it's complaining about (I suppose it doesn't like my gitlab instance has a self-signed certificate, also I am behind a proxy) and how can I inject my certificates or eventually ignore them.

Is there a way to do it?

Thanks

Vorherrschende Sprache
TypeScript
Sterne
3.9k
Forks
374
Ø Merge
21 Std. 18 Min.
Gemergte PRs (30 T.)
39

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus sourcebot-dev/sourcebot

Alle Issues in sourcebot-dev/sourcebot

Ähnliche Issues

Weitere Issues zu TypeScript

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.