From 81969554f4ceabdf96ce3e6181df6b88a32df00b Mon Sep 17 00:00:00 2001 From: LTek Date: Fri, 1 Sep 2023 13:26:12 +0200 Subject: [PATCH] clarify setup with gitlab with RFC1918 nets and non standard TLDs --- docs/docs/30-administration/11-forges/40-gitlab.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docs/30-administration/11-forges/40-gitlab.md b/docs/docs/30-administration/11-forges/40-gitlab.md index 46b40a0f1a..77ecdff829 100644 --- a/docs/docs/30-administration/11-forges/40-gitlab.md +++ b/docs/docs/30-administration/11-forges/40-gitlab.md @@ -25,7 +25,7 @@ You must register your application with GitLab in order to generate a Client and Please use `http://woodpecker.mycompany.com/authorize` as the Authorization callback URL. Grant `api` scope to the application. -If you run the Woodpecker CI server on the same host as the GitLab instance, you might also need to allow local connections in GitLab, otherwise API requests will fail. In GitLab, navigate to the Admin dashboard, then go to `Settings > Network > Outbound requests` and enable `Allow requests to the local network from web hooks and services`. +If you run the Woodpecker CI server on a prvate IP (RFC1918) or use a non standard TLD (e.g. `.local`, `.intern`) with your GitLab instance, you might also need to allow local connections in GitLab, otherwise API requests will fail. In GitLab, navigate to the Admin dashboard, then go to `Settings > Network > Outbound requests` and enable `Allow requests to the local network from web hooks and services`. ## Configuration