Skip to content

Commit 513a9ff

Browse files
committed
add ssl cert troubleshoot steps to docs:
1 parent 0d26dda commit 513a9ff

File tree

2 files changed

+5
-0
lines changed

2 files changed

+5
-0
lines changed

docs/docs/connections/bitbucket-data-center.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -79,6 +79,10 @@ Next, provide the access token to Sourcebot:
7979

8080
<BitbucketToken />
8181

82+
## Troubleshooting
83+
If you're seeing errors like `TypeError: fetch failed` when fetching repo info, it may be that Sourcebot is refusing to connect to your self-hosted Bitbucket instance due to unrecognized SSL certs. Try setting the `NODE_TLS_REJECT_UNAUTHORIZED=0` environment variable or providing Sourcebot your certs through the `NODE_EXTRA_CA_CERTS` environment variable.
84+
85+
8286

8387
## Schema reference
8488

docs/docs/connections/gitlab.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -159,6 +159,7 @@ To connect to a GitLab host other than `gitlab.com`, provide the `url` property
159159
## Troubleshooting
160160

161161
- If you're seeing errors like `GitbeakerTimeoutError: Query timeout was reached` when syncing a large number of projects, you can increase the client's timeout by setting the `GITLAB_CLIENT_QUERY_TIMEOUT_SECONDS` environment variable. [#162](https://github.com/sourcebot-dev/sourcebot/issues/162)
162+
- If you're seeing errors like `TypeError: fetch failed` when fetching user/project info, it may be that Sourcebot is refusing to connect to your self-hosted GitLab instance due to unrecognized SSL certs. Try setting the `NODE_TLS_REJECT_UNAUTHORIZED=0` environment variable or providing Sourcebot your certs through the `NODE_EXTRA_CA_CERTS` environment variable.
162163

163164
## Schema reference
164165

0 commit comments

Comments
 (0)