user1688
January 7, 2026, 6:41am
1
BugBot
I am an enterprise paid member and I am using a self-hosted GitLab instance. I have enabled Bugbot for my repository, but it does not respond at all—neither when I create a new pull request nor when I comment cursor review under an existing PR.
I tried commenting cursor review verbose=true, and the only response I received was:
Bugbot request id: serverGenReqId_d32e7f07-a611-4edc-82ce-a419efee459c
What could be causing this issue?
1. The GitLab instance is self-hosted.
2. Bugbot has been enabled for the repository.
MacOS
Version: 2.2.44 (Universal)
No - Cursor works, but with this issue
deanrie
January 7, 2026, 9:51am
2
Hey, thanks for the report.
To help narrow this down, could you please check a few things in your GitLab webhook settings:
Go to your GitLab project: Settings > Webhooks and find the Cursor webhook
Check Recent Deliveries. Do you see any failed deliveries or error codes?
Make sure these events are enabled: Push events and Merge request events
Click Test (Test > Merge request events). Do you get HTTP 200?
Also, can you confirm:
Are Cursor IPs allowlisted in your GitLab instance? (184.73.225.134, 3.209.66.12, 52.44.113.131)
Does Bugbot trigger only when a new MR is created, not on follow-up commits?
A similar issue is described here: Self hosted gitlab can not process follow up push . The team is looking into it.
user1688
January 7, 2026, 1:50pm
3
I confirm that I have received the message correctly, as shown in the screenshot.Creating a new MR did not trigger BugBot either.
deanrie
January 7, 2026, 4:57pm
4
Thanks for the info and the screenshot of the webhook settings. I can see the webhook is getting HTTP 200 responses.
This is a known issue with self-hosted GitLab instances. The team is working on a fix.
I’ll keep an eye on progress and update the thread as soon as I hear back from the team.
