Debug GitLab API

This page helps debug GitLab API connectivity issues.

Proxy Configuration Check

GitLab proxy status:
DOCUSAURUS_GITLAB_PROXY_URL: ✅ Set
Requests go to: https://chatbot.kern-ux.de/api/gitlab/api/v4/...

Test Basic Connectivity

Let's test if we can connect to the GitLab API:

Loading...

Solutions

1. Check the GitLab proxy

The components never talk to GitLab directly any more: they read through the anonymous, read-only GitLab proxy published by the KERN chatbot backend, which adds the credentials server-side. No GitLab API token is shipped to the browser.

If the check above reports no proxy, set the origin in your .env (copy .env.example first):

# defaults to $DOCUSAURUS_CHATBOT_URL/api/gitlab
DOCUSAURUS_GITLAB_PROXY_URL="https://chatbot.kern-ux.de/api/gitlab"

Restart the development server afterwards: npm start

2. Verify Project Path

The project path kern-ux/pattern-library should match the GitLab project URL: https://gitlab.opencode.de/kern-ux/pattern-library

The proxy only serves projects on its allowlist (GITLAB_PROXY_ALLOWED_PROJECTS in the chatbot backend) and only the issues, labels and milestones resources. Anything else answers 404 Not Found.

3. Check for CORS errors

The proxy answers with Access-Control-Allow-Origin: *, so any documentation host may read it. A failing request in the browser console usually means the proxy origin is wrong or the backend is unreachable.

---

💡 Check the browser console for detailed error messages and debug logs.