Certificate error
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
- Bereich
- backend, devops, networking
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
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
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus sourcebot-dev/sourcebot
-
bug triage needed
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
sourcebot-dev/sourcebot#1681 · 1 Kommentar ·
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
sourcebot-dev/sourcebot#1633 ·
-
bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 78/100
sourcebot-dev/sourcebot#1384 · 4 Kommentare ·
-
ask_sb bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
sourcebot-dev/sourcebot#1137 · 4 Kommentare ·
-
bug triage needed
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 48/100
sourcebot-dev/sourcebot#1661 · 1 Kommentar ·
Alle Issues in sourcebot-dev/sourcebot
Ähnliche Issues
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
bcgov/bc-wallet-mobile#4761 · 1 Kommentar ·
-
external-issue to-triage
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 88/100
-
area-deployment area-integrations triage:bot-seen
Schwierigkeit 2/5 Ein halber Tag Anfängerfreundlichkeit 86/100
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 82/100
-
refactor
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100