Error status code 422 trying to integrate version control with project about bytebase

[suzaku]

@linucksrox You may want to take a look at this document.

To prevent this type of exploitation from happening, starting with GitLab 10.6, all Webhook requests to the current GitLab instance server address and/or in a private network are forbidden by default. That means that all requests made to 127.0.0.1, ::1 and 0.0.0.0, as well as IPv4 10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16 and IPv6 site-local (ffc0::/10) addresses aren’t allowed.

If it's the case for you, you can solve this problem by changing this behavior on GitLab Settings.

[tianzhou]

Reopen this as we should also mention this directly in the product. Having Bytebase and GitLab in the same private network is a very likely setup.

[suzaku]

Yes, I think the error message should mention this. I can help with this.

[suzaku]

I have something different in mind. We should avoid overburden users with information in the happy-path UI, instead, we can show the tips in the error prompt when we know it's most useful the the user.

SGTM. BTW, if you also want to improve the backend error message. The code is around here https://github.com/bytebase/bytebase/blob/main/server/project.go#L191-L192

:) I know, already testing the change in my environment. The frontend environment seems to be broken, PTAL at #109

[suzaku]

@tianzhou Please assign this issue to me to avoid duplicate works on it.

[tianzhou]

Thanks for the report, we will take a look and follow up soon.

[tianzhou]

Unable to reproduce for now.

@linucksrox could you please provide your GitLab version?

Also could you please paste the message on the console after supplying the --debug option on startup https://docs.bytebase.com/reference/command-line#debug

[linucksrox]

I tried again after enabling debug mode, and the output was this:
bytebase_bytebase.1.taax3az06lfg@docker181 | {"time":"2021-12-03T14:11:42Z","method":"POST","uri":"/api/project/101/repository","status":500,"error":"code=500, message=Failed to create webhook for project ID: 101, status code: 422"}

Thank you for pointing me in the right direction with the Gitlab webhook settings! I was able to get it working by checking "Allow requests to the local network from web hooks and services." and also adding the bytebase domain name in the allow list.

[tianzhou]

Thanks @suzaku to point out the right direction. Add this to the troubleshoot guide https://docs.bytebase.com/use-bytebase/vcs-integration/troubleshoot#failed-to-create-webhook-xxx-status-code-422-for-gitlab

[tianzhou]

@suzaku I am also thinking to include a note around here https://github.com/bytebase/bytebase/blob/main/frontend/src/components/RepositorySetupWizard.vue#L4

This message stays on the top during the entire VCS setup process.

[suzaku]

I have something different in mind.
We should avoid overburden users with information in the happy-path UI, instead, we can show the tips in the error prompt when we know it's most useful the the user.

[tianzhou]

I have something different in mind. We should avoid overburden users with information in the happy-path UI, instead, we can show the tips in the error prompt when we know it's most useful the the user.

SGTM. BTW, if you also want to improve the backend error message. The code is around here https://github.com/bytebase/bytebase/blob/main/server/project.go#L191-L192