From fc594197b3cdb691b0681b88f4d7e4676321d56e Mon Sep 17 00:00:00 2001 From: Marcin Jasion <5058132+mjasion@users.noreply.github.com> Date: Wed, 26 Jul 2023 20:43:29 +0200 Subject: [PATCH] docs: Provide information about Studio Public IPs (#4727) Co-authored-by: Marcin Jasion --- content/docs/studio/troubleshooting.md | 18 ++++++++++++++++++ .../user-guide/connect-custom-gitlab-server.md | 17 +++++++++++++++++ 2 files changed, 35 insertions(+) diff --git a/content/docs/studio/troubleshooting.md b/content/docs/studio/troubleshooting.md index 0a6dd1e094..ea5143da54 100644 --- a/content/docs/studio/troubleshooting.md +++ b/content/docs/studio/troubleshooting.md @@ -98,6 +98,24 @@ incorrect, you will see one of the following errors: - Credentials are either broken or not recognized - No permission to fetch remote data +### Errors related to DVC remotes behind firewall + +For self-hosted S3 storage(like Minio) or SSH server, ensure that it is +available to access from the internet. If your server is behind the firewall, +you can limit the traffic on the firewall to the server to allow access from our +IP addresses only, which are: + +``` +3.21.85.173/32 +3.142.203.124/32 +``` + +Additionally, if you provide the hostname, the DNS records associated with the +storage server should be publicly available to resolve the server name. Use +[DNS Propagation Checker](https://www.whatsmydns.net/) to confirm if the server +domain is resolvable. If you still have any trouble setting up the connection to +your server, please [contact us](/doc/studio/troubleshooting#support). + ## Error: No data found to visualize If you have connected to a non-DVC repository, then you need to specify custom diff --git a/content/docs/studio/user-guide/connect-custom-gitlab-server.md b/content/docs/studio/user-guide/connect-custom-gitlab-server.md index e9d127dfc1..d4f4633cdd 100644 --- a/content/docs/studio/user-guide/connect-custom-gitlab-server.md +++ b/content/docs/studio/user-guide/connect-custom-gitlab-server.md @@ -49,3 +49,20 @@ Custom GitLab server support is available only within a team workspace, and is available to all Iterative Studio teams (free and paid). + +## My GitLab server is behind a firewall. What should I do? + +Firstly, the GitLab server must be exposed to the internet to enable remote +access from the Studio. You can limit the traffic on the firewall to the server +to allow access from our IP addresses only, which are: + +``` +3.21.85.173/32 +3.142.203.124/32 +``` + +Additionally, the DNS records associated with the GitLab server should be +publicly available to resolve the server name. Use +[DNS Propagation Checker](https://www.whatsmydns.net/) to confirm if the GitLab +domain is resolvable. If you still have any trouble setting up the connection to +your GitLab server, please [contact us](/doc/studio/troubleshooting#support).