From 3816c3097d61a0a4dd76f645ab3563d3721f72da Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 28 Aug 2026 16:24:47 +0000 Subject: [PATCH 1/4] docs: clarify network direction and egress IP for self-hosted Git integrations --- deploy/ghes.mdx | 20 ++++++++++--------- deploy/gitlab-self-hosted.mdx | 14 +++++++++++++ docs.json | 3 ++- ...-addresses-for-git-provider-allowlists.mdx | 19 ++++++++++++++++++ 4 files changed, 46 insertions(+), 10 deletions(-) create mode 100644 help-center/ip-addresses-for-git-provider-allowlists.mdx diff --git a/deploy/ghes.mdx b/deploy/ghes.mdx index f543c38630..45a8b047aa 100644 --- a/deploy/ghes.mdx +++ b/deploy/ghes.mdx @@ -16,18 +16,20 @@ If you use a cloud-hosted GitHub instance, see the [GitHub](/deploy/github) page ### Network requirements -#### Outbound connectivity +The integration requires traffic in both directions between your GHES instance and Mintlify. Configure your firewall to allow both of the following connections. -Your GitHub Enterprise Server must be able to reach: -- Mintlify's API endpoints (https://leaves.mintlify.com) -- Webhook receivers (port 443) +#### Outbound: your GHES instance to Mintlify -#### Firewall configuration +Your GHES instance delivers webhook events to Mintlify over HTTPS (port 443) at `leaves.mintlify.com`. -Allow the following outbound connections: -- Connections from Mintlify's static IP: `54.242.90.151` -- HTTPS (port 443) to Mintlify's service domains -- DNS resolution for Mintlify's service domains +- Allow outbound HTTPS (port 443) to `leaves.mintlify.com`. Allow this traffic by hostname. Mintlify does not publish a static IP address list for this endpoint, and its underlying IP addresses can change. +- Ensure your GHES instance can resolve `leaves.mintlify.com` through DNS. If your servers use an internal DNS resolver, confirm that it resolves public hostnames. + +#### Inbound: Mintlify to your GHES instance + +Mintlify connects to your GHES instance over HTTPS (port 443) to call the GitHub API and clone repositories. These connections originate from Mintlify's static egress IP address: `54.242.90.151`. + +If a firewall or IP allowlist restricts access to your GHES instance, allow inbound HTTPS (port 443) from `54.242.90.151`. ## Step 1: register the GitHub App diff --git a/deploy/gitlab-self-hosted.mdx b/deploy/gitlab-self-hosted.mdx index 7ecbb3667e..7544b00fa5 100644 --- a/deploy/gitlab-self-hosted.mdx +++ b/deploy/gitlab-self-hosted.mdx @@ -21,6 +21,20 @@ Unlike gitlab.com, where Mintlify ships a single OAuth application that every cu - A Mintlify organization on the **Pro or Enterprise plan**. - A Mintlify organization that has the self-hosted GitLab feature enabled. Contact support if you don't see the **Self-hosted GitLab** section in your [Git settings](https://app.mintlify.com/settings/deployment/git-settings) dashboard page. +## Network requirements + +The integration requires traffic in both directions between your GitLab instance and Mintlify. + +### Inbound: Mintlify to your GitLab instance + +Mintlify connects to your GitLab instance over HTTPS (port 443) to exchange OAuth tokens, call the GitLab API, clone repositories, and push commits. These connections originate from Mintlify's static egress IP address: `54.242.90.151`. + +If a firewall or IP allowlist restricts access to your GitLab instance, allow inbound HTTPS (port 443) from `54.242.90.151`. + +### Outbound: your GitLab instance to Mintlify + +Your GitLab instance delivers webhook events to Mintlify over HTTPS (port 443) at `app.mintlify.com`. Allow this traffic by hostname. Mintlify does not publish a static IP address list for this endpoint. + ## Set up the connection diff --git a/docs.json b/docs.json index b6562bbe72..e054d0eaee 100644 --- a/docs.json +++ b/docs.json @@ -483,7 +483,8 @@ "help-center/configure-oauth-with-auth0", "help-center/private-repo-missing-when-creating-second-deployment", "help-center/static-file-not-served", - "help-center/preview-deployment-not-created-for-fork-branch" + "help-center/preview-deployment-not-created-for-fork-branch", + "help-center/ip-addresses-for-git-provider-allowlists" ] } ] diff --git a/help-center/ip-addresses-for-git-provider-allowlists.mdx b/help-center/ip-addresses-for-git-provider-allowlists.mdx new file mode 100644 index 0000000000..5e16620d9f --- /dev/null +++ b/help-center/ip-addresses-for-git-provider-allowlists.mdx @@ -0,0 +1,19 @@ +--- +title: "What IP addresses does Mintlify connect to my Git provider from?" +description: "Add Mintlify's static egress IP address to the allowlist of your GitHub Enterprise Cloud organization, GitHub Enterprise Server instance, or self-hosted GitLab instance." +keywords: ["egress IP", "IP allowlist", "firewall", "static IP", "GitHub Enterprise", "GHES", "self-hosted GitLab", "54.242.90.151"] +--- + +If your Git provider sits behind an IP allowlist or firewall, you need to allow the connections Mintlify makes to it. Mintlify connects to Git providers over HTTPS (port 443) from a single static egress IP address: + +``` +54.242.90.151 +``` + +Add this IP address to your allowlist when: + +- Your GitHub Enterprise Cloud organization has an IP allowlist enabled. See [GitHub Enterprise with IP allowlists](/deploy/github#github-enterprise-with-ip-allowlists). +- A firewall or IP allowlist restricts inbound access to your GitHub Enterprise Server instance. See the [GHES network requirements](/deploy/ghes#network-requirements). +- A firewall or IP allowlist restricts inbound access to your self-hosted GitLab instance. See the [self-hosted GitLab network requirements](/deploy/gitlab-self-hosted#network-requirements). + +Traffic in the other direction, from your Git server to Mintlify, works differently. Your instance delivers webhook events to Mintlify hostnames such as `leaves.mintlify.com` and `app.mintlify.com`. Allow that outbound traffic by hostname. Mintlify does not publish a static IP address list for those endpoints, and their underlying IP addresses can change. From 5dec3e6bea33710ca686dafcbf9fdd6f2da96735 Mon Sep 17 00:00:00 2001 From: "mintlify[bot]" <109931778+mintlify[bot]@users.noreply.github.com> Date: Fri, 28 Aug 2026 16:32:31 +0000 Subject: [PATCH 2/4] docs: translate network requirement updates into es, fr, zh and tune SEO metadata --- es.json | 3 ++- es/deploy/ghes.mdx | 22 +++++++++---------- es/deploy/gitlab-self-hosted.mdx | 20 +++++++++++++++++ ...-addresses-for-git-provider-allowlists.mdx | 19 ++++++++++++++++ fr.json | 3 ++- fr/deploy/ghes.mdx | 22 +++++++++---------- fr/deploy/gitlab-self-hosted.mdx | 20 +++++++++++++++++ ...-addresses-for-git-provider-allowlists.mdx | 19 ++++++++++++++++ ...-addresses-for-git-provider-allowlists.mdx | 4 ++-- zh.json | 3 ++- zh/deploy/ghes.mdx | 22 +++++++++---------- zh/deploy/gitlab-self-hosted.mdx | 20 +++++++++++++++++ ...-addresses-for-git-provider-allowlists.mdx | 19 ++++++++++++++++ 13 files changed, 158 insertions(+), 38 deletions(-) create mode 100644 es/help-center/ip-addresses-for-git-provider-allowlists.mdx create mode 100644 fr/help-center/ip-addresses-for-git-provider-allowlists.mdx create mode 100644 zh/help-center/ip-addresses-for-git-provider-allowlists.mdx diff --git a/es.json b/es.json index 37fb44e73c..019f2c5a12 100644 --- a/es.json +++ b/es.json @@ -461,7 +461,8 @@ "es/help-center/configure-oauth-with-auth0", "es/help-center/private-repo-missing-when-creating-second-deployment", "es/help-center/static-file-not-served", - "es/help-center/preview-deployment-not-created-for-fork-branch" + "es/help-center/preview-deployment-not-created-for-fork-branch", + "es/help-center/ip-addresses-for-git-provider-allowlists" ] } ] diff --git a/es/deploy/ghes.mdx b/es/deploy/ghes.mdx index 4ecc4993c7..71e8dc5b77 100644 --- a/es/deploy/ghes.mdx +++ b/es/deploy/ghes.mdx @@ -20,24 +20,24 @@ Si usas una instancia de GitHub alojada en la nube, consulta la página de [GitH ### Requisitos de red -
- #### Conectividad saliente +La integración requiere tráfico en ambas direcciones entre tu instancia de GHES y Mintlify. Configura tu firewall para permitir las dos conexiones siguientes. + +
+ #### Saliente: de tu instancia de GHES a Mintlify
-Tu servidor de GitHub Enterprise debe poder acceder a: +Tu instancia de GHES entrega eventos de webhook a Mintlify mediante HTTPS (puerto 443) en `leaves.mintlify.com`. -* Los endpoints de la API de Mintlify (https://leaves.mintlify.com) -* Los receptores de webhooks (puerto 443) +* Permite HTTPS saliente (puerto 443) hacia `leaves.mintlify.com`. Permite este tráfico por nombre de host. Mintlify no publica una lista de direcciones IP estáticas para este endpoint, y sus direcciones IP subyacentes pueden cambiar. +* Asegúrate de que tu instancia de GHES pueda resolver `leaves.mintlify.com` mediante DNS. Si tus servidores usan un resolutor de DNS interno, confirma que resuelva nombres de host públicos. -
- #### Configuración del firewall +
+ #### Entrante: de Mintlify a tu instancia de GHES
-Permite las siguientes conexiones salientes: +Mintlify se conecta a tu instancia de GHES mediante HTTPS (puerto 443) para llamar a la API de GitHub y clonar repositorios. Estas conexiones se originan desde la dirección IP de salida estática de Mintlify: `54.242.90.151`. -* Conexiones desde la IP estática de Mintlify: `54.242.90.151` -* HTTPS (puerto 443) a los dominios de servicio de Mintlify -* Resolución de DNS para los dominios de servicio de Mintlify +Si un firewall o una lista de IP permitidas restringe el acceso a tu instancia de GHES, permite HTTPS entrante (puerto 443) desde `54.242.90.151`.
## Paso 1: Registrar la aplicación de GitHub diff --git a/es/deploy/gitlab-self-hosted.mdx b/es/deploy/gitlab-self-hosted.mdx index 55ce774e9c..999e43254e 100644 --- a/es/deploy/gitlab-self-hosted.mdx +++ b/es/deploy/gitlab-self-hosted.mdx @@ -23,6 +23,26 @@ A diferencia de gitlab.com, donde Mintlify proporciona una única aplicación OA - Una organización de Mintlify en el **plan Pro o superior**. - Una organización de Mintlify que tenga habilitada la función de GitLab autoalojado. Contacta con soporte si no ves la sección **Self-hosted GitLab** en la página del dashboard [Git settings](https://app.mintlify.com/settings/deployment/git-settings). +
+ ## Requisitos de red +
+ +La integración requiere tráfico en ambas direcciones entre tu instancia de GitLab y Mintlify. + +
+ ### Entrante: de Mintlify a tu instancia de GitLab +
+ +Mintlify se conecta a tu instancia de GitLab mediante HTTPS (puerto 443) para intercambiar tokens de OAuth, llamar a la API de GitLab, clonar repositorios y enviar commits. Estas conexiones se originan desde la dirección IP de salida estática de Mintlify: `54.242.90.151`. + +Si un firewall o una lista de IP permitidas restringe el acceso a tu instancia de GitLab, permite HTTPS entrante (puerto 443) desde `54.242.90.151`. + +
+ ### Saliente: de tu instancia de GitLab a Mintlify +
+ +Tu instancia de GitLab entrega eventos de webhook a Mintlify mediante HTTPS (puerto 443) en `app.mintlify.com`. Permite este tráfico por nombre de host. Mintlify no publica una lista de direcciones IP estáticas para este endpoint. +
## Configura la conexión
diff --git a/es/help-center/ip-addresses-for-git-provider-allowlists.mdx b/es/help-center/ip-addresses-for-git-provider-allowlists.mdx new file mode 100644 index 0000000000..e510c8c611 --- /dev/null +++ b/es/help-center/ip-addresses-for-git-provider-allowlists.mdx @@ -0,0 +1,19 @@ +--- +title: "¿Desde qué IPs se conecta Mintlify a mi proveedor de Git?" +description: "Añade la IP de salida estática de Mintlify, 54.242.90.151, a la lista de permitidos para GitHub Enterprise Cloud, GitHub Enterprise Server e instancias autoalojadas de GitLab." +keywords: ["IP de salida", "lista de IP permitidas", "firewall", "IP estática", "GitHub Enterprise", "GHES", "GitLab autoalojado", "54.242.90.151"] +--- + +Si tu proveedor de Git está detrás de una lista de IP permitidas o de un firewall, debes permitir las conexiones que Mintlify realiza hacia él. Mintlify se conecta a los proveedores de Git mediante HTTPS (puerto 443) desde una única dirección IP de salida estática: + +``` +54.242.90.151 +``` + +Añade esta dirección IP a tu lista de permitidos cuando: + +- Tu organización de GitHub Enterprise Cloud tiene habilitada una lista de IP permitidas. Consulta [GitHub Enterprise con listas de IP permitidas](/es/deploy/github#github-enterprise-with-ip-allowlists). +- Un firewall o una lista de IP permitidas restringe el acceso entrante a tu instancia de GitHub Enterprise Server. Consulta los [requisitos de red de GHES](/es/deploy/ghes#network-requirements). +- Un firewall o una lista de IP permitidas restringe el acceso entrante a tu instancia autoalojada de GitLab. Consulta los [requisitos de red de GitLab autoalojado](/es/deploy/gitlab-self-hosted#network-requirements). + +El tráfico en la otra dirección, de tu servidor de Git a Mintlify, funciona de manera distinta. Tu instancia entrega eventos de webhook a nombres de host de Mintlify como `leaves.mintlify.com` y `app.mintlify.com`. Permite ese tráfico saliente por nombre de host. Mintlify no publica una lista de direcciones IP estáticas para esos endpoints, y sus direcciones IP subyacentes pueden cambiar. diff --git a/fr.json b/fr.json index efbce353ec..166ee58073 100644 --- a/fr.json +++ b/fr.json @@ -461,7 +461,8 @@ "fr/help-center/configure-oauth-with-auth0", "fr/help-center/private-repo-missing-when-creating-second-deployment", "fr/help-center/static-file-not-served", - "fr/help-center/preview-deployment-not-created-for-fork-branch" + "fr/help-center/preview-deployment-not-created-for-fork-branch", + "fr/help-center/ip-addresses-for-git-provider-allowlists" ] } ] diff --git a/fr/deploy/ghes.mdx b/fr/deploy/ghes.mdx index e0befae1cf..c0912de4a0 100644 --- a/fr/deploy/ghes.mdx +++ b/fr/deploy/ghes.mdx @@ -20,24 +20,24 @@ Si vous utilisez une instance GitHub hébergée sur le cloud, consultez la page ### Prérequis réseau
-
- #### Connectivité sortante +L'intégration nécessite du trafic dans les deux sens entre votre instance GHES et Mintlify. Configurez votre pare-feu pour autoriser les deux connexions suivantes. + +
+ #### Sortant : de votre instance GHES vers Mintlify
-Votre GitHub Enterprise Server doit pouvoir accéder à : +Votre instance GHES envoie les événements de webhook à Mintlify via HTTPS (port 443) à l'adresse `leaves.mintlify.com`. -* les points de terminaison de l'API Mintlify (https://leaves.mintlify.com) -* les récepteurs de webhook (port 443) +* Autorisez le HTTPS sortant (port 443) vers `leaves.mintlify.com`. Autorisez ce trafic par nom d'hôte. Mintlify ne publie pas de liste d'adresses IP statiques pour ce point de terminaison, et ses adresses IP sous-jacentes peuvent changer. +* Assurez-vous que votre instance GHES peut résoudre `leaves.mintlify.com` via DNS. Si vos serveurs utilisent un résolveur DNS interne, vérifiez qu'il résout les noms d'hôte publics. -
- #### Configuration du pare-feu +
+ #### Entrant : de Mintlify vers votre instance GHES
-Autorisez les connexions sortantes suivantes : +Mintlify se connecte à votre instance GHES via HTTPS (port 443) pour appeler l'API GitHub et cloner des dépôts. Ces connexions proviennent de l'adresse IP de sortie statique de Mintlify : `54.242.90.151`. -* Connexions provenant de l'adresse IP statique de Mintlify : `54.242.90.151` -* HTTPS (port 443) vers les domaines de service de Mintlify -* Résolution DNS pour les domaines de service de Mintlify +Si un pare-feu ou une liste d'autorisation d'adresses IP restreint l'accès à votre instance GHES, autorisez le HTTPS entrant (port 443) depuis `54.242.90.151`.
## Étape 1 : Enregistrer l'application GitHub diff --git a/fr/deploy/gitlab-self-hosted.mdx b/fr/deploy/gitlab-self-hosted.mdx index efa380921c..bba173043a 100644 --- a/fr/deploy/gitlab-self-hosted.mdx +++ b/fr/deploy/gitlab-self-hosted.mdx @@ -23,6 +23,26 @@ Contrairement à gitlab.com, où Mintlify fournit une seule application OAuth co - Une organisation Mintlify avec un **plan Pro ou supérieur**. - Une organisation Mintlify pour laquelle la fonctionnalité GitLab auto-hébergé est activée. Contactez le support si vous ne voyez pas la section **Self-hosted GitLab** dans la page de votre tableau de bord [Git settings](https://app.mintlify.com/settings/deployment/git-settings). +
+ ## Prérequis réseau +
+ +L'intégration nécessite du trafic dans les deux sens entre votre instance GitLab et Mintlify. + +
+ ### Entrant : de Mintlify vers votre instance GitLab +
+ +Mintlify se connecte à votre instance GitLab via HTTPS (port 443) pour échanger des jetons OAuth, appeler l'API GitLab, cloner des référentiels et pousser des commits. Ces connexions proviennent de l'adresse IP de sortie statique de Mintlify : `54.242.90.151`. + +Si un pare-feu ou une liste d'autorisation d'adresses IP restreint l'accès à votre instance GitLab, autorisez le HTTPS entrant (port 443) depuis `54.242.90.151`. + +
+ ### Sortant : de votre instance GitLab vers Mintlify +
+ +Votre instance GitLab envoie les événements de webhook à Mintlify via HTTPS (port 443) à l'adresse `app.mintlify.com`. Autorisez ce trafic par nom d'hôte. Mintlify ne publie pas de liste d'adresses IP statiques pour ce point de terminaison. +
## Configurer la connexion
diff --git a/fr/help-center/ip-addresses-for-git-provider-allowlists.mdx b/fr/help-center/ip-addresses-for-git-provider-allowlists.mdx new file mode 100644 index 0000000000..fa2ea441a6 --- /dev/null +++ b/fr/help-center/ip-addresses-for-git-provider-allowlists.mdx @@ -0,0 +1,19 @@ +--- +title: "Depuis quelles IP Mintlify se connecte-t-il à mon fournisseur Git ?" +description: "Ajoutez l'IP de sortie statique de Mintlify 54.242.90.151 à votre liste d'autorisation pour GitHub Enterprise Cloud, GitHub Enterprise Server et les instances GitLab auto-hébergées." +keywords: ["IP de sortie", "liste d'autorisation IP", "pare-feu", "IP statique", "GitHub Enterprise", "GHES", "GitLab auto-hébergé", "54.242.90.151"] +--- + +Si votre fournisseur Git se trouve derrière une liste d'autorisation d'adresses IP ou un pare-feu, vous devez autoriser les connexions que Mintlify établit vers celui-ci. Mintlify se connecte aux fournisseurs Git via HTTPS (port 443) depuis une seule adresse IP de sortie statique : + +``` +54.242.90.151 +``` + +Ajoutez cette adresse IP à votre liste d'autorisation lorsque : + +- Votre organisation GitHub Enterprise Cloud a une liste d'autorisation d'adresses IP activée. Consultez [GitHub Enterprise avec listes d'autorisation IP](/fr/deploy/github#github-enterprise-with-ip-allowlists). +- Un pare-feu ou une liste d'autorisation d'adresses IP restreint l'accès entrant à votre instance GitHub Enterprise Server. Consultez les [prérequis réseau GHES](/fr/deploy/ghes#network-requirements). +- Un pare-feu ou une liste d'autorisation d'adresses IP restreint l'accès entrant à votre instance GitLab auto-hébergée. Consultez les [prérequis réseau du GitLab auto-hébergé](/fr/deploy/gitlab-self-hosted#network-requirements). + +Le trafic dans l'autre sens, de votre serveur Git vers Mintlify, fonctionne différemment. Votre instance envoie les événements de webhook à des noms d'hôte Mintlify tels que `leaves.mintlify.com` et `app.mintlify.com`. Autorisez ce trafic sortant par nom d'hôte. Mintlify ne publie pas de liste d'adresses IP statiques pour ces points de terminaison, et leurs adresses IP sous-jacentes peuvent changer. diff --git a/help-center/ip-addresses-for-git-provider-allowlists.mdx b/help-center/ip-addresses-for-git-provider-allowlists.mdx index 5e16620d9f..946f29b3a0 100644 --- a/help-center/ip-addresses-for-git-provider-allowlists.mdx +++ b/help-center/ip-addresses-for-git-provider-allowlists.mdx @@ -1,6 +1,6 @@ --- -title: "What IP addresses does Mintlify connect to my Git provider from?" -description: "Add Mintlify's static egress IP address to the allowlist of your GitHub Enterprise Cloud organization, GitHub Enterprise Server instance, or self-hosted GitLab instance." +title: "What IPs does Mintlify connect to my Git provider from?" +description: "Allowlist Mintlify's static egress IP 54.242.90.151 for GitHub Enterprise Cloud, GitHub Enterprise Server, and self-hosted GitLab instances." keywords: ["egress IP", "IP allowlist", "firewall", "static IP", "GitHub Enterprise", "GHES", "self-hosted GitLab", "54.242.90.151"] --- diff --git a/zh.json b/zh.json index 60bd65fb5c..d2ac6f4927 100644 --- a/zh.json +++ b/zh.json @@ -461,7 +461,8 @@ "zh/help-center/configure-oauth-with-auth0", "zh/help-center/private-repo-missing-when-creating-second-deployment", "zh/help-center/static-file-not-served", - "zh/help-center/preview-deployment-not-created-for-fork-branch" + "zh/help-center/preview-deployment-not-created-for-fork-branch", + "zh/help-center/ip-addresses-for-git-provider-allowlists" ] } ] diff --git a/zh/deploy/ghes.mdx b/zh/deploy/ghes.mdx index 4de2df91b2..7debd97dba 100644 --- a/zh/deploy/ghes.mdx +++ b/zh/deploy/ghes.mdx @@ -20,24 +20,24 @@ keywords: ["GitHub Enterprise Server", "GHES", "GitHub Enterprise"] ### 网络要求
-
- #### 出站连接 +该集成需要在你的 GHES 实例与 Mintlify 之间建立双向通信。请配置防火墙，允许以下两个方向的连接。 + +
+ #### 出站：你的 GHES 实例到 Mintlify
-你的 GitHub Enterprise Server 必须能够访问： +你的 GHES 实例会通过 HTTPS（端口 443）向 `leaves.mintlify.com` 投递 webhook 事件。 -* Mintlify 的 API 端点 (https://leaves.mintlify.com) -* Webhook 接收端（443 端口） +* 允许到 `leaves.mintlify.com` 的出站 HTTPS（端口 443）连接。请按主机名放行此流量。Mintlify 不会为该端点发布静态 IP 地址列表，且其底层 IP 地址可能发生变化。 +* 确保你的 GHES 实例可以通过 DNS 解析 `leaves.mintlify.com`。如果你的服务器使用内部 DNS 解析器，请确认它能够解析公共主机名。 -
- #### 防火墙配置 +
+ #### 入站：Mintlify 到你的 GHES 实例
-请允许以下出站连接： +Mintlify 会通过 HTTPS（端口 443）连接你的 GHES 实例，用于调用 GitHub API 和克隆仓库。这些连接来自 Mintlify 的静态出口 IP 地址：`54.242.90.151`。 -* 来自 Mintlify 静态 IP 地址的连接：`54.242.90.151` -* 到 Mintlify 服务域名的 HTTPS（端口 443）连接 -* 对 Mintlify 服务域名的 DNS 解析 +如果防火墙或 IP 允许列表限制了对你的 GHES 实例的访问，请允许来自 `54.242.90.151` 的入站 HTTPS（端口 443）连接。
## 步骤 1：注册 GitHub 应用 diff --git a/zh/deploy/gitlab-self-hosted.mdx b/zh/deploy/gitlab-self-hosted.mdx index 011e0f492f..a447d4493f 100644 --- a/zh/deploy/gitlab-self-hosted.mdx +++ b/zh/deploy/gitlab-self-hosted.mdx @@ -23,6 +23,26 @@ keywords: ["GitLab", "自托管", "OAuth", "自动化", "企业"] - 你的 Mintlify 组织需要 **Pro 或更高套餐**。 - 你的 Mintlify 组织已启用自托管 GitLab 功能。如果你在 [Git 设置](https://app.mintlify.com/settings/deployment/git-settings)控制台页面中未看到 **Self-hosted GitLab** 部分，请联系支持团队。 +
+ ## 网络要求 +
+ +该集成需要在你的 GitLab 实例与 Mintlify 之间建立双向通信。 + +
+ ### 入站：Mintlify 到你的 GitLab 实例 +
+ +Mintlify 会通过 HTTPS（端口 443）连接你的 GitLab 实例，用于交换 OAuth 令牌、调用 GitLab API、克隆存储库和推送提交。这些连接来自 Mintlify 的静态出口 IP 地址：`54.242.90.151`。 + +如果防火墙或 IP 允许列表限制了对你的 GitLab 实例的访问，请允许来自 `54.242.90.151` 的入站 HTTPS（端口 443）连接。 + +
+ ### 出站：你的 GitLab 实例到 Mintlify +
+ +你的 GitLab 实例会通过 HTTPS（端口 443）向 `app.mintlify.com` 投递 webhook 事件。请按主机名放行此流量。Mintlify 不会为该端点发布静态 IP 地址列表。 +
## 设置连接
diff --git a/zh/help-center/ip-addresses-for-git-provider-allowlists.mdx b/zh/help-center/ip-addresses-for-git-provider-allowlists.mdx new file mode 100644 index 0000000000..dae62c2ab4 --- /dev/null +++ b/zh/help-center/ip-addresses-for-git-provider-allowlists.mdx @@ -0,0 +1,19 @@ +--- +title: "Mintlify 从哪些 IP 连接到我的 Git 提供商？" +description: "为 GitHub Enterprise Cloud、GitHub Enterprise Server 和自托管 GitLab 实例将 Mintlify 的静态出口 IP 54.242.90.151 加入允许列表。" +keywords: ["出口 IP", "IP 允许列表", "防火墙", "静态 IP", "GitHub Enterprise", "GHES", "自托管 GitLab", "54.242.90.151"] +--- + +如果你的 Git 提供商位于 IP 允许列表或防火墙之后，你需要放行 Mintlify 对它发起的连接。Mintlify 通过 HTTPS（端口 443）从单个静态出口 IP 地址连接 Git 提供商： + +``` +54.242.90.151 +``` + +在以下情况下，请将该 IP 地址添加到你的允许列表： + +- 你的 GitHub Enterprise Cloud 组织启用了 IP 允许列表。参见[启用 IP 允许列表的 GitHub Enterprise](/zh/deploy/github#github-enterprise-with-ip-allowlists)。 +- 防火墙或 IP 允许列表限制了对你的 GitHub Enterprise Server 实例的入站访问。参见 [GHES 网络要求](/zh/deploy/ghes#network-requirements)。 +- 防火墙或 IP 允许列表限制了对你的自托管 GitLab 实例的入站访问。参见[自托管 GitLab 网络要求](/zh/deploy/gitlab-self-hosted#network-requirements)。 + +另一个方向的流量（从你的 Git 服务器到 Mintlify）的工作方式有所不同。你的实例会向 `leaves.mintlify.com` 和 `app.mintlify.com` 等 Mintlify 主机名投递 webhook 事件。请按主机名放行这类出站流量。Mintlify 不会为这些端点发布静态 IP 地址列表，且其底层 IP 地址可能发生变化。 From f77703ca1959f584f670fcef2af2a65f2246af2d Mon Sep 17 00:00:00 2001 From: Rohan Godha Date: Wed, 2 Sep 2026 15:36:47 -0700 Subject: [PATCH 3/4] Updated mintlify pages - Updated deploy/ghes.mdx - Updated deploy/gitlab-self-hosted.mdx Mintlify-Source: dashboard-editor --- deploy/ghes.mdx | 319 +++++++++++++++++----------------- deploy/gitlab-self-hosted.mdx | 15 +- 2 files changed, 167 insertions(+), 167 deletions(-) diff --git a/deploy/ghes.mdx b/deploy/ghes.mdx index 45a8b047aa..724a4f7e63 100644 --- a/deploy/ghes.mdx +++ b/deploy/ghes.mdx @@ -1,7 +1,10 @@ --- title: "GitHub Enterprise Server" description: "Install and configure the Mintlify GitHub App on your GitHub Enterprise Server instance for automated documentation deployments and syncing." -keywords: ["GitHub Enterprise Server", "GHES", "GitHub Enterprise"] +keywords: + - "GitHub Enterprise Server" + - "GHES" + - "GitHub Enterprise" --- This guide walks you through setting up the Mintlify GitHub App on your GitHub Enterprise Server (GHES) installation. To connect a GHES instance to Mintlify, you must create a local version of our app within your self-hosted environment that communicates with our remote server. @@ -36,123 +39,115 @@ If a firewall or IP allowlist restricts access to your GHES instance, allow inbo See [Registering a GitHub App](https://docs.github.com/en/enterprise-server@3.18/apps/creating-github-apps/registering-a-github-app/registering-a-github-app) in the GitHub documentation for detailed instructions. - -1. In the upper-right corner of any page on GitHub, click your profile picture. -2. Click **Your organizations**. -3. Click **Settings** next to the organization that you want to create the app for. - - - -1. In the left sidebar, click **Developer settings**. -2. Click **GitHub Apps**. -3. Click **New GitHub App**. - - - -Set the following: - -- **GitHub App name:** `Mintlify` -- **Description:** `Integration with Mintlify services` -- **Homepage URL:** `https://mintlify.com` -- **User authorization callback URL:** `https://your-github-server.com/` (replace with your actual GHES domain) - - + + 1. In the upper-right corner of any page on GitHub, click your profile picture. + 2. Click **Your organizations**. + 3. Click **Settings** next to the organization that you want to create the app for. + + + 1. In the left sidebar, click **Developer settings**. + 2. Click **GitHub Apps**. + 3. Click **New GitHub App**. + + + Set the following: + + - **GitHub App name:** `Mintlify` + - **Description:** `Integration with Mintlify services` + - **Homepage URL:** `https://mintlify.com` + - **User authorization callback URL:** `https://your-github-server.com/` (replace with your actual GHES domain) + ## Step 2: configure app permissions - -Set the following permissions for the app. The app needs no Organization, Account, or Enterprise permissions: - -- **Checks:** Read and write -- **Contents:** Read and write -- **Deployments:** Read and write -- **Metadata:** Read-only -- **Pull Requests:** Read and write - - - -Select the following webhook events: - -- Installation -- Installation Target -- Create -- Delete -- Public -- Pull Request -- Push -- Repository - + + Set the following permissions for the app. The app needs no Organization, Account, or Enterprise permissions: + + - **Checks:** Read and write + - **Contents:** Read and write + - **Deployments:** Read and write + - **Metadata:** Read-only + - **Pull Requests:** Read and write + + + Select the following webhook events: + + - Installation + - Installation Target + - Create + - Delete + - Public + - Pull Request + - Push + - Repository + ## Step 3: generate and secure credentials - -Click **Create GitHub App**. - -GitHub redirects you to the app's settings page. - - - -1. Scroll down to the **Private keys** section. -2. Click **Generate a private key**. -3. Download the `.pem` file and securely store it. - - - -Record the following: - -- **App ID** (visible at the top of the settings page) -- **Client ID** (in the "About" section) -- **Client Secret** (generate and record it securely) - + + Click **Create GitHub App**. + + GitHub redirects you to the app's settings page. + + + 1. Scroll down to the **Private keys** section. + 2. Click **Generate a private key**. + 3. Download the `.pem` file and securely store it. + + + Record the following: + + - **App ID** (visible at the top of the settings page) + - **Client ID** (in the "About" section) + - **Client Secret** (generate and record it securely) + ## Step 4: install the app - -1. From the app settings page, click **Install App** in the left sidebar. -2. Select your organization from the list. - - - -Select either: - -- **All repositories** (for organization-wide access) -- **Only select repositories** (choose specific repositories) - - - - -1. Click **Install**. -2. Record the installation ID from the URL. For example, in `https://your-github-server.com/settings/installations/12345`, the string `12345` is the installation ID. - + + 1. From the app settings page, click **Install App** in the left sidebar. + 2. Select your organization from the list. + + + Select either: + + - **All repositories** (for organization-wide access) + - **Only select repositories** (choose specific repositories) + + + 1. Click **Install**. + 2. Record the installation ID from the URL. For example, in `https://your-github-server.com/settings/installations/12345`, the string `12345` is the installation ID. + ## Step 5: configure webhook URL - -1. Go back to your app's settings page. -2. Scroll to the **Webhook** section. - - - -Configure the following: - -- **Webhook URL:** `https://leaves.mintlify.com/github-enterprise/:subdomain` (replace `:subdomain` with the URL that we provide you with) -- **Webhook secret:** Generate a random string (32+ characters) and record it securely. Mintlify can also generate this and provide it to you. - + + 1. Go back to your app's settings page. + 2. Scroll to the **Webhook** section. + + + Configure the following: + + - **Webhook URL:** `https://leaves.mintlify.com/github-enterprise/:subdomain` (replace `:subdomain` with the URL that we provide you with) + - **Webhook secret:** Generate a random string (32+ characters) and record it securely. Mintlify can also generate this and provide it to you. + ## Share credentials with us + Share the following information with our team using your secure information transfer method of choice. ### Required credentials -- GitHub Enterprise Server base URL: https://your-github-server.com + +- GitHub Enterprise Server base URL: [https://your-github-server.com](https://your-github-server.com) - App ID: (from step 3) - App client ID: (from step 3) - App client secret: (from step 3) @@ -162,10 +157,12 @@ Share the following information with our team using your secure information tran - Webhook secret: (from step 5) ### Optional credentials for troubleshooting + - Repository names: Specific repositories where you installed the app - GitHub Enterprise Server version: Found in your site admin dashboard ## Mintlify connection + We take the credentials you provide us and store them, encrypted, in a secure location. Then we work with you to either: - Integrate your GHES environment with an existing Mintlify deployment. @@ -174,84 +171,82 @@ We take the credentials you provide us and store them, encrypted, in a secure lo After you integrate your GHES environment with a Mintlify deployment, you are ready to enable webhooks for your GitHub App. -The webhook URL may change based on our configuration. We test the integration and provide you with the new URL. + The webhook URL may change based on our configuration. We test the integration and provide you with the new URL. ## Test the integration - -1. Go to your GitHub App settings. -2. Click the **Advanced** tab. -3. Check "Recent Deliveries" for successful webhook deliveries. -4. Look for HTTP 200 responses. - - - -1. Create a test issue or pull request in an installed repository. -2. Verify that Mintlify responds appropriately. - + + 1. Go to your GitHub App settings. + 2. Click the **Advanced** tab. + 3. Check "Recent Deliveries" for successful webhook deliveries. + 4. Look for HTTP 200 responses. + + + 1. Create a test issue or pull request in an installed repository. + 2. Verify that Mintlify responds appropriately. + ## FAQ and troubleshooting - -Ensure you have: - -- Site admin privileges for app creation. -- Organization owner or admin rights for app installation. -- Proper repository permissions if installing on specific repositories. - - - -- Verify the webhook URL is correct and accessible. -- Ensure your firewall allows outbound HTTPS connections. -- Check the webhook secret matches what you configured. -- Review webhook delivery logs in the "Advanced" tab of your GitHub App settings. - - - -Your GHES might use self-signed certificates. Our services cannot verify your server's certificate. - -**Solution:** Ensure your GHES has a valid SSL certificate. - - - -- Ensure our server receives and acknowledges webhooks with response code 200. -- You granted the required permissions during installation. - - - -Yes, during installation you can select "Only select repositories" and choose specific ones. You can modify this later in your organization's installed apps settings. This is the recommended form of installation. - - - -- Go to the app settings as a site admin. -- Modify permissions as needed. -- The app needs to be re-approved by organization owners. -- Notify us of any permission changes so we can advise on any additional steps you may need. - - - -You must: - -- Add our service domains to your firewall allowlist. -- Ensure outbound HTTPS (port 443) connectivity. -- If direct internet access is not allowed, set up a proxy. - - - -No, your GHES must be able to communicate with our cloud-hosted server. - - - -Reach out to your customer success representative at Mintlify, or contact our support team at support@mintlify.com with: - -- Your GitHub Enterprise Server version. -- Specific error messages. -- Screenshots of any issues. -- Network/firewall configuration details (if relevant). - + + Ensure you have: + + - Site admin privileges for app creation. + - Organization owner or admin rights for app installation. + - Proper repository permissions if installing on specific repositories. + + + + - Verify the webhook URL is correct and accessible. + - Ensure your firewall allows outbound HTTPS connections. + - Check the webhook secret matches what you configured. + - Review webhook delivery logs in the "Advanced" tab of your GitHub App settings. + + + + Your GHES might use self-signed certificates. Our services cannot verify your server's certificate. + + **Solution:** Ensure your GHES has a valid SSL certificate. + + + + - Ensure our server receives and acknowledges webhooks with response code 200. + - You granted the required permissions during installation. + + + + Yes, during installation you can select "Only select repositories" and choose specific ones. You can modify this later in your organization's installed apps settings. This is the recommended form of installation. + + + + - Go to the app settings as a site admin. + - Modify permissions as needed. + - The app needs to be re-approved by organization owners. + - Notify us of any permission changes so we can advise on any additional steps you may need. + + + + You must: + + - Add our service domains to your firewall allowlist. + - Ensure outbound HTTPS (port 443) connectivity. + - If direct internet access is not allowed, set up a proxy. + + + + No, your GHES must be able to communicate with our cloud-hosted server. + + + + Reach out to your customer success representative at Mintlify, or contact our support team at [support@mintlify.com](mailto:support@mintlify.com) with: + + - Your GitHub Enterprise Server version. + - Specific error messages. + - Screenshots of any issues. + - Network/firewall configuration details (if relevant). + - diff --git a/deploy/gitlab-self-hosted.mdx b/deploy/gitlab-self-hosted.mdx index 7544b00fa5..f2403e06c2 100644 --- a/deploy/gitlab-self-hosted.mdx +++ b/deploy/gitlab-self-hosted.mdx @@ -1,7 +1,12 @@ --- title: "Self-hosted GitLab OAuth" description: "Connect a self-hosted GitLab instance to Mintlify via OAuth so automations can clone repositories, push commits, and open merge requests on your behalf." -keywords: ["GitLab", "self-hosted", "OAuth", "automations", "enterprise"] +keywords: + - "GitLab" + - "self-hosted" + - "OAuth" + - "automations" + - "enterprise" --- Mintlify supports OAuth-based authorization for self-hosted GitLab instances, in addition to gitlab.com. OAuth lets the Mintlify agent act as a GitLab user during automation runs: cloning repositories, pushing commits, opening merge requests, and registering project webhooks. @@ -39,7 +44,7 @@ Your GitLab instance delivers webhook events to Mintlify over HTTPS (port 443) a - In your self-hosted GitLab, sign in as an admin and navigate to **Admin Area** \> **Applications** \> **Add new application**. + In your self-hosted GitLab, sign in as an admin and navigate to **Admin Area** > **Applications** > **Add new application**. Configure the application with these values: @@ -59,7 +64,7 @@ Your GitLab instance delivers webhook events to Mintlify over HTTPS (port 443) a After saving, GitLab displays the application's **Application ID** and **Secret**. Keep this page open. GitLab only shows the secret once. - In your Mintlify dashboard, open **Settings** \> **Git settings** and find the **Self-hosted GitLab** section under **GitLab OAuth**. + In your Mintlify dashboard, open **Settings** > **Git settings** and find the **Self-hosted GitLab** section under **GitLab OAuth**. Click **Connect Self-Hosted GitLab** and enter: @@ -113,11 +118,11 @@ Fix: rotate credentials following the [Rotate credentials](#rotate-credentials) GitLab refused to register the webhook because its outbound-request allowlist rejected the URL Mintlify sent (`https://app.mintlify.com/gitlab-oauth-webhook`). Self-hosted instances reject "local" URLs unless the admin explicitly allows them. -Fix: in your GitLab admin area, go to **Settings** \> **Network** \> **Outbound requests** and enable **Allow requests to the local network from webhooks and integrations**. If your network policy blocks `app.mintlify.com`, contact your network admin to allow outbound HTTPS to that host. +Fix: in your GitLab admin area, go to **Settings** > **Network** > **Outbound requests** and enable **Allow requests to the local network from webhooks and integrations**. If your network policy blocks `app.mintlify.com`, contact your network admin to allow outbound HTTPS to that host. ### No consent screen on authorize If you don't see GitLab's consent dialog when authorizing, either: - The application carries the **Trusted** flag on GitLab. Trusted applications skip consent for all users. Clear the **Trusted** checkbox in the application settings if you want users to see and confirm scopes. -- Your GitLab user has previously authorized the application with the same scopes. GitLab remembers prior grants and skips consent on subsequent authorizes. Revoke the application authorization in **User settings** \> **Applications** \> **Authorized applications** to see consent again. \ No newline at end of file +- Your GitLab user has previously authorized the application with the same scopes. GitLab remembers prior grants and skips consent on subsequent authorizes. Revoke the application authorization in **User settings** > **Applications** > **Authorized applications** to see consent again. From f7a9007d847566a7646a079b038a6d2960e7735f Mon Sep 17 00:00:00 2001 From: Ethan Palm Date: Tue, 8 Sep 2026 17:07:45 -0700 Subject: [PATCH 4/4] Merge main and revise Git network requirements Resolves the nav conflicts with #7276 and narrows this PR to the substantive content changes. - Correct the static-IP claims. 54.242.90.151 is the platform's egress IP (API calls, check runs, deployment statuses). Agent sandboxes use dynamic IPs unless support enables the static-egress-proxy flag for a deployment, so clone/push is no longer attributed to the static IP. This removes the contradiction with help-center/agent-blocked-by-git-provider-ip-allow-list (#7276) and cross-links it from all three pages. - Revert the Steps reindentation in deploy/ghes.mdx, leaving only the network requirements rewrite. - Revert the hand-edited es/fr/zh files and nav entries; translations run automatically after merge. - Add a language tag to the IP code block and fix Vale term errors. Co-Authored-By: Claude Opus 5 (1M context) --- deploy/ghes.mdx | 24 ++++++++++++------- deploy/gitlab-self-hosted.mdx | 21 ++++++++-------- ...-addresses-for-git-provider-allowlists.mdx | 16 +++++++++---- 3 files changed, 36 insertions(+), 25 deletions(-) diff --git a/deploy/ghes.mdx b/deploy/ghes.mdx index f543c38630..780eca8203 100644 --- a/deploy/ghes.mdx +++ b/deploy/ghes.mdx @@ -16,18 +16,24 @@ If you use a cloud-hosted GitHub instance, see the [GitHub](/deploy/github) page ### Network requirements -#### Outbound connectivity +The integration requires traffic in both directions between your GHES instance and Mintlify. Configure your firewall to allow both of the following connections. -Your GitHub Enterprise Server must be able to reach: -- Mintlify's API endpoints (https://leaves.mintlify.com) -- Webhook receivers (port 443) +#### Outbound: your GHES instance to Mintlify -#### Firewall configuration +Your GHES instance delivers webhook events to Mintlify over HTTPS (port 443) at `leaves.mintlify.com`. -Allow the following outbound connections: -- Connections from Mintlify's static IP: `54.242.90.151` -- HTTPS (port 443) to Mintlify's service domains -- DNS resolution for Mintlify's service domains +- Allow outbound HTTPS (port 443) to `leaves.mintlify.com`. Allow this traffic by hostname. Mintlify does not publish a static IP address list for this endpoint, and its underlying IP addresses can change. +- Ensure your GHES instance can resolve `leaves.mintlify.com` through DNS. If your servers use an internal DNS resolver, confirm that it resolves public hostnames. + +#### Inbound: Mintlify to your GHES instance + +Mintlify connects to your GHES instance over HTTPS (port 443) to call the GitHub API, report check run and deployment statuses, and read repository content. These connections originate from Mintlify's static egress IP address: `54.242.90.151`. + +If a firewall or IP allowlist restricts access to your GHES instance, allow inbound HTTPS (port 443) from `54.242.90.151`. + + + [Agent](/agent) runs clone and push from separate sandbox infrastructure that uses dynamic IP addresses by default. If your GHES instance enforces an IP allowlist, see [Fix agent runs blocked by an IP allow list](/help-center/agent-blocked-by-git-provider-ip-allow-list). + ## Step 1: register the GitHub App diff --git a/deploy/gitlab-self-hosted.mdx b/deploy/gitlab-self-hosted.mdx index e2fbfbbeae..b94660a60e 100644 --- a/deploy/gitlab-self-hosted.mdx +++ b/deploy/gitlab-self-hosted.mdx @@ -1,12 +1,7 @@ --- title: "Self-hosted GitLab OAuth" description: "Connect a self-hosted GitLab instance to Mintlify via OAuth so automations can clone repositories, push commits, and open merge requests on your behalf." -keywords: - - "GitLab" - - "self-hosted" - - "OAuth" - - "automations" - - "enterprise" +keywords: ["GitLab", "self-hosted", "OAuth", "automations", "enterprise"] --- Mintlify supports OAuth-based authorization for self-hosted GitLab instances, in addition to gitlab.com. OAuth lets the Mintlify agent act as a GitLab user during automation runs: cloning repositories, pushing commits, opening merge requests, and registering project webhooks. @@ -32,10 +27,14 @@ The integration requires traffic in both directions between your GitLab instance ### Inbound: Mintlify to your GitLab instance -Mintlify connects to your GitLab instance over HTTPS (port 443) to exchange OAuth tokens, call the GitLab API, clone repositories, and push commits. These connections originate from Mintlify's static egress IP address: `54.242.90.151`. +Mintlify connects to your GitLab instance over HTTPS (port 443) to exchange OAuth tokens and call the GitLab API. These connections originate from Mintlify's static egress IP address: `54.242.90.151`. If a firewall or IP allowlist restricts access to your GitLab instance, allow inbound HTTPS (port 443) from `54.242.90.151`. + + Automation runs clone and push from separate sandbox infrastructure that uses dynamic IP addresses by default. If your GitLab instance enforces an IP allowlist, see [Fix agent runs blocked by an IP allow list](/help-center/agent-blocked-by-git-provider-ip-allow-list). + + ### Outbound: your GitLab instance to Mintlify Your GitLab instance delivers webhook events to Mintlify over HTTPS (port 443) at `app.mintlify.com`. Allow this traffic by hostname. Mintlify does not publish a static IP address list for this endpoint. @@ -44,7 +43,7 @@ Your GitLab instance delivers webhook events to Mintlify over HTTPS (port 443) a - In your self-hosted GitLab, sign in as an admin and navigate to **Admin Area** > **Applications** > **Add new application**. + In your self-hosted GitLab, sign in as an admin and navigate to **Admin Area** \> **Applications** \> **Add new application**. Configure the application with these values: @@ -64,7 +63,7 @@ Your GitLab instance delivers webhook events to Mintlify over HTTPS (port 443) a After saving, GitLab displays the application's **Application ID** and **Secret**. Keep this page open. GitLab only shows the secret once. - In your Mintlify dashboard, open **Settings** > **Git settings** and find the **Self-hosted GitLab** section under **GitLab OAuth**. + In your Mintlify dashboard, open **Settings** \> **Git settings** and find the **Self-hosted GitLab** section under **GitLab OAuth**. Click **Connect Self-Hosted GitLab** and enter: @@ -118,11 +117,11 @@ Fix: rotate credentials following the [Rotate credentials](#rotate-credentials) GitLab refused to register the webhook because its outbound-request allowlist rejected the URL Mintlify sent (`https://app.mintlify.com/gitlab-oauth-webhook`). Self-hosted instances reject "local" URLs unless the admin explicitly allows them. -Fix: in your GitLab admin area, go to **Settings** > **Network** > **Outbound requests** and enable **Allow requests to the local network from webhooks and integrations**. If your network policy blocks `app.mintlify.com`, contact your network admin to allow outbound HTTPS to that host. +Fix: in your GitLab admin area, go to **Settings** \> **Network** \> **Outbound requests** and enable **Allow requests to the local network from webhooks and integrations**. If your network policy blocks `app.mintlify.com`, contact your network admin to allow outbound HTTPS to that host. ### No consent screen on authorize If you don't see GitLab's consent dialog when authorizing, either: - The application carries the **Trusted** flag on GitLab. Trusted applications skip consent for all users. Clear the **Trusted** checkbox in the application settings if you want users to see and confirm scopes. -- Your GitLab user has previously authorized the application with the same scopes. GitLab remembers prior grants and skips consent on subsequent authorizes. Revoke the application authorization in **User settings** > **Applications** > **Authorized applications** to see consent again. +- Your GitLab user has previously authorized the application with the same scopes. GitLab remembers prior grants and skips consent on subsequent authorizes. Revoke the application authorization in **User settings** \> **Applications** \> **Authorized applications** to see consent again. \ No newline at end of file diff --git a/help-center/ip-addresses-for-git-provider-allowlists.mdx b/help-center/ip-addresses-for-git-provider-allowlists.mdx index 946f29b3a0..86151507d8 100644 --- a/help-center/ip-addresses-for-git-provider-allowlists.mdx +++ b/help-center/ip-addresses-for-git-provider-allowlists.mdx @@ -1,12 +1,12 @@ --- -title: "What IPs does Mintlify connect to my Git provider from?" -description: "Allowlist Mintlify's static egress IP 54.242.90.151 for GitHub Enterprise Cloud, GitHub Enterprise Server, and self-hosted GitLab instances." +title: "What IP addresses does Mintlify connect to a Git provider from?" +description: "Add Mintlify's static egress IP 54.242.90.151 to the allowlist for GitHub Enterprise Cloud, GitHub Enterprise Server, and self-hosted GitLab instances." keywords: ["egress IP", "IP allowlist", "firewall", "static IP", "GitHub Enterprise", "GHES", "self-hosted GitLab", "54.242.90.151"] --- -If your Git provider sits behind an IP allowlist or firewall, you need to allow the connections Mintlify makes to it. Mintlify connects to Git providers over HTTPS (port 443) from a single static egress IP address: +If your Git provider sits behind an IP allowlist or firewall, you need to allow the connections Mintlify makes to it. Mintlify's platform connects to Git providers over HTTPS (port 443) from a single static egress IP address: -``` +```text 54.242.90.151 ``` @@ -16,4 +16,10 @@ Add this IP address to your allowlist when: - A firewall or IP allowlist restricts inbound access to your GitHub Enterprise Server instance. See the [GHES network requirements](/deploy/ghes#network-requirements). - A firewall or IP allowlist restricts inbound access to your self-hosted GitLab instance. See the [self-hosted GitLab network requirements](/deploy/gitlab-self-hosted#network-requirements). -Traffic in the other direction, from your Git server to Mintlify, works differently. Your instance delivers webhook events to Mintlify hostnames such as `leaves.mintlify.com` and `app.mintlify.com`. Allow that outbound traffic by hostname. Mintlify does not publish a static IP address list for those endpoints, and their underlying IP addresses can change. +## Agent and automation runs + +[Agent](/agent) runs clone and push from separate sandbox infrastructure. That traffic uses dynamic IP addresses by default, so allowlisting `54.242.90.151` does not cover it. Mintlify support can route a deployment's agent Git traffic through the static IP on request. See [Fix agent runs blocked by an IP allow list](/help-center/agent-blocked-by-git-provider-ip-allow-list). + +## Traffic from your Git server to Mintlify + +Traffic in the other direction works differently. Your instance delivers webhook events to Mintlify hostnames such as `leaves.mintlify.com` and `app.mintlify.com`. Allow that outbound traffic by hostname. Mintlify does not publish a static IP address list for those endpoints, and their underlying IP addresses can change.