Firewall requirements

Your firewall must be configured for P4 DAM to work correctly. P4 Server, P4 Search, and Elasticsearch must be all reachable from where P4 DAM is installed.

If you have connection issues when deploying P4 DAM, P4 Search, and Elasticsearch on separate hosts, you can temporarily configure inter‑service connections using IP addresses to help rule out failure points.

IP‑based configuration is not tested and might cause browser‑related issues, such as CORS errors, if P4 Search pages are accessed directly. If issues continue, contact Perforce Support.

Inbound connections

To allow users access to P4 DAM via web browsers and version control clients, ensure the P4 DAM server is reachable by the following connections:

  • TCP 22 - Version control access over SSH.
  • TCP 80 - Web application and version control access over HTTP.
  • TCP 443 - Web application and version control access over HTTPS (only if SSL/TLS is used).

Inter-server connections

For Enterprise deployments, the following connections are required:

  • TCP 4002 from P4 DAM Web to TeamHub DB server - Access to MongoDB database.
  • TCP 6379 from P4 DAM Web to TeamHub DB server - Access to Redis database.

For convenience, check the arrows and corresponding ports for deployment type, and then reference here for a more detailed explanation of the port usage.

Outbound connections

P4 DAM might use several external services for mailing, authentication, and so on.

If external services are required, ensure the following connections are open for P4 DAM servers to access:

  • TCP [usually 25] to use SMTP gateway for mailing.
  • TCP 1601 for P4 Search.
  • TCP 9200 (default) for Elasticsearch
  • Reachable P4 Server on your specified P4PORT