Skip to content

fix(perforce): Add IP allowlisting guidance to Perforce docs #16850

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
mujacica merged 1 commit into from
Mar 10, 2026
Merged

fix(perforce): Add IP allowlisting guidance to Perforce docs #16850

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 2 additions & 1 deletion docs/organization/integrations/source-code-mgmt/perforce/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:<host>:<port> 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.

<Alert title="Note">

Expand Down Expand Up @@ -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:<host>:<port> trust -y`
- Your firewall allows inbound connections on the Perforce port (typically 1666).

Expand Down
Loading