From f15340537f6317005522ffd582633244f5163b19 Mon Sep 17 00:00:00 2001 From: Amir Mujacic Date: Mon, 9 Mar 2026 15:17:48 -0700 Subject: [PATCH] fix(perforce): Add IP allowlisting guidance to Perforce docs Explicitly document that users must allowlist Sentry's outbound IP addresses in their firewall configuration, matching the guidance already present in the GitHub Enterprise docs. --- .../integrations/source-code-mgmt/perforce/index.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/organization/integrations/source-code-mgmt/perforce/index.mdx b/docs/organization/integrations/source-code-mgmt/perforce/index.mdx index cfdb7aeda869b..a3c248b6f4160 100644 --- a/docs/organization/integrations/source-code-mgmt/perforce/index.mdx +++ b/docs/organization/integrations/source-code-mgmt/perforce/index.mdx @@ -35,7 +35,7 @@ Before installing, make sure you have: - **Sentry permissions**: Organization owner, manager, or admin role. - **Perforce server access**: A Perforce user account with read access to the depots you want to connect. We recommend creating a dedicated service account (e.g., `sentry-bot`). - **SSL fingerprint** (if using SSL): Obtain it by running `p4 -p ssl:: trust -y` on a machine with access to your Perforce server. -- **Network connectivity**: The Sentry application must be able to reach your Perforce server over the network on the configured port. +- **Network connectivity**: The Sentry application must be able to reach your Perforce server over the network on the configured port. Make sure the [IP addresses Sentry uses to make outbound requests](/security-legal-pii/security/ip-ranges/) are allowed by your firewall or network configuration. @@ -162,6 +162,7 @@ The following features are **not supported** by the Perforce integration: If you see "Failed to connect to Perforce server", verify: - Your P4PORT address is correct and reachable from Sentry's network. +- The [IP addresses Sentry uses to make outbound requests](/security-legal-pii/security/ip-ranges/) are allowed by your firewall or network configuration. - If using SSL, ensure the SSL fingerprint is correct. Re-obtain it with: `p4 -p ssl:: trust -y` - Your firewall allows inbound connections on the Perforce port (typically 1666).