diff options
| author | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-28 18:10:57 +0300 |
|---|---|---|
| committer | GitLab Bot <gitlab-bot@gitlab.com> | 2023-08-28 18:10:57 +0300 |
| commit | 8b992ba2281a5da786195b1fd1c2e424b0f441c4 (patch) | |
| tree | be10d68e606c202dc837ad0d32b03256d6cf8326 /doc/administration/pages | |
| parent | 62a3deaa9f6e1e1986c43b49a41a917201ec2734 (diff) | |
Add latest changes from gitlab-org/gitlab@master
Diffstat (limited to 'doc/administration/pages')
| -rw-r--r-- | doc/administration/pages/troubleshooting.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/administration/pages/troubleshooting.md b/doc/administration/pages/troubleshooting.md index a103c793763..9f335dc7d9c 100644 --- a/doc/administration/pages/troubleshooting.md +++ b/doc/administration/pages/troubleshooting.md @@ -152,7 +152,7 @@ This can happen to GitLab instances with multiple servers running both the core GitLab application and GitLab Pages. This can also happen when a single container is running both the core GitLab application and GitLab Pages. -AWS [recommends using an IP target type](https://aws.amazon.com/premiumsupport/knowledge-center/target-connection-fails-load-balancer/) +AWS [recommends using an IP target type](https://repost.aws/knowledge-center/target-connection-fails-load-balancer) to resolve this issue. Turning off [client IP preservation](https://docs.aws.amazon.com/elasticloadbalancing/latest/network/load-balancer-target-groups.html#client-ip-preservation) |