mirror of
https://github.com/woodpecker-ci/woodpecker.git
synced 2025-02-17 03:45:13 +00:00
clarify setup with gitlab with RFC1918 nets and non standard TLDs (#2363)
The current documentation mentions that when one uses woodpecker on the same host as Gitlab, you might need to set the `Allow requests to the local network from webhooks and integrations` option on the gitlab server. This option not only needs to be set when running on the same host, but also needs to be set when setting up woodpecker with Gitlab on any RFC1918 net and on any non standard TLD like `.local` or `.internal`.
This commit is contained in:
parent
cf16d0ce2d
commit
3bee51dc7a
1 changed files with 1 additions and 1 deletions
|
@ -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
|
||||
|
||||
|
|
Loading…
Reference in a new issue