diff --git a/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/gitlab-eece.mdx index fe44aab88..d45ffd5b6 100644 --- a/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -57,8 +57,6 @@ Leave the page open in a browser tab. In the next step you will copy values from ~> **Important:** The account you use for connecting HCP Terraform **must have admin (master) access** to any shared repositories of Terraform configurations, since creating webhooks requires admin permissions. Do not create the application as an administrative application not owned by a user; HCP Terraform needs user access to repositories to create webhooks and ingress configurations. - ~> **Important**: In GitLab CE or EE 10.6 and up, you may also need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. - 2. Navigate to GitLab's "User Settings > Applications" page. This page is located at `https:///profile/applications`. You can also reach it through GitLab's menus: diff --git a/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..43c8074ff 100644 --- a/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202501-1/docs/enterprise/vcs/troubleshooting.mdx @@ -84,6 +84,12 @@ This usually happens when an SSH key isn't associated with the VCS provider's OA Note that the "SSH Key" section in a workspace's settings is only used for mid-run operations like cloning Terraform modules. It isn't used when cloning the linked repository before a run. +## GitLab CE / GitLab EE + +### "Error creating workspace - Failed to create webhook on repository: Failed to create webhook on repository: terraform/tfe: Server responded with code 422, message: Invalid url given. Request URI: ``" + +In GitLab CE or EE 10.6 and up, you may need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. + ## General The following errors may occur for all VCS providers except Bitbucket Data Center. diff --git a/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/gitlab-eece.mdx index fe44aab88..d45ffd5b6 100644 --- a/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -57,8 +57,6 @@ Leave the page open in a browser tab. In the next step you will copy values from ~> **Important:** The account you use for connecting HCP Terraform **must have admin (master) access** to any shared repositories of Terraform configurations, since creating webhooks requires admin permissions. Do not create the application as an administrative application not owned by a user; HCP Terraform needs user access to repositories to create webhooks and ingress configurations. - ~> **Important**: In GitLab CE or EE 10.6 and up, you may also need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. - 2. Navigate to GitLab's "User Settings > Applications" page. This page is located at `https:///profile/applications`. You can also reach it through GitLab's menus: diff --git a/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..43c8074ff 100644 --- a/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202502-1/docs/enterprise/vcs/troubleshooting.mdx @@ -84,6 +84,12 @@ This usually happens when an SSH key isn't associated with the VCS provider's OA Note that the "SSH Key" section in a workspace's settings is only used for mid-run operations like cloning Terraform modules. It isn't used when cloning the linked repository before a run. +## GitLab CE / GitLab EE + +### "Error creating workspace - Failed to create webhook on repository: Failed to create webhook on repository: terraform/tfe: Server responded with code 422, message: Invalid url given. Request URI: ``" + +In GitLab CE or EE 10.6 and up, you may need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. + ## General The following errors may occur for all VCS providers except Bitbucket Data Center. diff --git a/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/gitlab-eece.mdx index fe44aab88..d45ffd5b6 100644 --- a/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/gitlab-eece.mdx @@ -57,8 +57,6 @@ Leave the page open in a browser tab. In the next step you will copy values from ~> **Important:** The account you use for connecting HCP Terraform **must have admin (master) access** to any shared repositories of Terraform configurations, since creating webhooks requires admin permissions. Do not create the application as an administrative application not owned by a user; HCP Terraform needs user access to repositories to create webhooks and ingress configurations. - ~> **Important**: In GitLab CE or EE 10.6 and up, you may also need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. - 2. Navigate to GitLab's "User Settings > Applications" page. This page is located at `https:///profile/applications`. You can also reach it through GitLab's menus: diff --git a/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..43c8074ff 100644 --- a/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202502-2/docs/enterprise/vcs/troubleshooting.mdx @@ -84,6 +84,12 @@ This usually happens when an SSH key isn't associated with the VCS provider's OA Note that the "SSH Key" section in a workspace's settings is only used for mid-run operations like cloning Terraform modules. It isn't used when cloning the linked repository before a run. +## GitLab CE / GitLab EE + +### "Error creating workspace - Failed to create webhook on repository: Failed to create webhook on repository: terraform/tfe: Server responded with code 422, message: Invalid url given. Request URI: ``" + +In GitLab CE or EE 10.6 and up, you may need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. + ## General The following errors may occur for all VCS providers except Bitbucket Data Center. diff --git a/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/gitlab-eece.mdx index fe44aab88..d45ffd5b6 100644 --- a/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -57,8 +57,6 @@ Leave the page open in a browser tab. In the next step you will copy values from ~> **Important:** The account you use for connecting HCP Terraform **must have admin (master) access** to any shared repositories of Terraform configurations, since creating webhooks requires admin permissions. Do not create the application as an administrative application not owned by a user; HCP Terraform needs user access to repositories to create webhooks and ingress configurations. - ~> **Important**: In GitLab CE or EE 10.6 and up, you may also need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. - 2. Navigate to GitLab's "User Settings > Applications" page. This page is located at `https:///profile/applications`. You can also reach it through GitLab's menus: diff --git a/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..43c8074ff 100644 --- a/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202503-1/docs/enterprise/vcs/troubleshooting.mdx @@ -84,6 +84,12 @@ This usually happens when an SSH key isn't associated with the VCS provider's OA Note that the "SSH Key" section in a workspace's settings is only used for mid-run operations like cloning Terraform modules. It isn't used when cloning the linked repository before a run. +## GitLab CE / GitLab EE + +### "Error creating workspace - Failed to create webhook on repository: Failed to create webhook on repository: terraform/tfe: Server responded with code 422, message: Invalid url given. Request URI: ``" + +In GitLab CE or EE 10.6 and up, you may need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. + ## General The following errors may occur for all VCS providers except Bitbucket Data Center. diff --git a/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/gitlab-eece.mdx index a4b484859..43debfc07 100644 --- a/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -57,8 +57,6 @@ Leave the page open in a browser tab. In the next step you will copy values from ~> **Important:** The account you use for connecting HCP Terraform **must have admin (master) access** to any shared repositories of Terraform configurations, since creating webhooks requires admin permissions. Do not create the application as an administrative application not owned by a user; HCP Terraform needs user access to repositories to create webhooks and ingress configurations. - ~> **Important**: In GitLab CE or EE 10.6 and up, you may also need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. - 2. Navigate to GitLab's "User Settings > Applications" page. This page is located at `https:///profile/applications`. You can also reach it through GitLab's menus: diff --git a/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..43c8074ff 100644 --- a/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202504-1/docs/enterprise/vcs/troubleshooting.mdx @@ -84,6 +84,12 @@ This usually happens when an SSH key isn't associated with the VCS provider's OA Note that the "SSH Key" section in a workspace's settings is only used for mid-run operations like cloning Terraform modules. It isn't used when cloning the linked repository before a run. +## GitLab CE / GitLab EE + +### "Error creating workspace - Failed to create webhook on repository: Failed to create webhook on repository: terraform/tfe: Server responded with code 422, message: Invalid url given. Request URI: ``" + +In GitLab CE or EE 10.6 and up, you may need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. + ## General The following errors may occur for all VCS providers except Bitbucket Data Center. diff --git a/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/gitlab-eece.mdx index a4b484859..43debfc07 100644 --- a/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -57,8 +57,6 @@ Leave the page open in a browser tab. In the next step you will copy values from ~> **Important:** The account you use for connecting HCP Terraform **must have admin (master) access** to any shared repositories of Terraform configurations, since creating webhooks requires admin permissions. Do not create the application as an administrative application not owned by a user; HCP Terraform needs user access to repositories to create webhooks and ingress configurations. - ~> **Important**: In GitLab CE or EE 10.6 and up, you may also need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. - 2. Navigate to GitLab's "User Settings > Applications" page. This page is located at `https:///profile/applications`. You can also reach it through GitLab's menus: diff --git a/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..43c8074ff 100644 --- a/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202505-1/docs/enterprise/vcs/troubleshooting.mdx @@ -84,6 +84,12 @@ This usually happens when an SSH key isn't associated with the VCS provider's OA Note that the "SSH Key" section in a workspace's settings is only used for mid-run operations like cloning Terraform modules. It isn't used when cloning the linked repository before a run. +## GitLab CE / GitLab EE + +### "Error creating workspace - Failed to create webhook on repository: Failed to create webhook on repository: terraform/tfe: Server responded with code 422, message: Invalid url given. Request URI: ``" + +In GitLab CE or EE 10.6 and up, you may need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. + ## General The following errors may occur for all VCS providers except Bitbucket Data Center. diff --git a/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/gitlab-eece.mdx b/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/gitlab-eece.mdx index a4b484859..43debfc07 100644 --- a/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/gitlab-eece.mdx +++ b/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/gitlab-eece.mdx @@ -57,8 +57,6 @@ Leave the page open in a browser tab. In the next step you will copy values from ~> **Important:** The account you use for connecting HCP Terraform **must have admin (master) access** to any shared repositories of Terraform configurations, since creating webhooks requires admin permissions. Do not create the application as an administrative application not owned by a user; HCP Terraform needs user access to repositories to create webhooks and ingress configurations. - ~> **Important**: In GitLab CE or EE 10.6 and up, you may also need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. - 2. Navigate to GitLab's "User Settings > Applications" page. This page is located at `https:///profile/applications`. You can also reach it through GitLab's menus: diff --git a/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/troubleshooting.mdx b/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/troubleshooting.mdx index 182c9ba0b..43c8074ff 100644 --- a/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/troubleshooting.mdx +++ b/content/terraform-enterprise/v202506-1/docs/enterprise/vcs/troubleshooting.mdx @@ -84,6 +84,12 @@ This usually happens when an SSH key isn't associated with the VCS provider's OA Note that the "SSH Key" section in a workspace's settings is only used for mid-run operations like cloning Terraform modules. It isn't used when cloning the linked repository before a run. +## GitLab CE / GitLab EE + +### "Error creating workspace - Failed to create webhook on repository: Failed to create webhook on repository: terraform/tfe: Server responded with code 422, message: Invalid url given. Request URI: ``" + +In GitLab CE or EE 10.6 and up, you may need to enable **Allow requests to the local network from hooks and services** on the "Outbound requests" section inside the Admin area under Settings (`/admin/application_settings/network`). Refer to [the GitLab documentation](https://docs.gitlab.com/ee/security/webhooks.html) for details. + ## General The following errors may occur for all VCS providers except Bitbucket Data Center.