Communicating port information

Helix Core Server applications need to know on what machine the p4d service is listening, on which TCP/IP port p4d is listening, and whether to communicate in plaintext or over SSL.

Set each Helix Core Server user’s P4PORT environment variable to protocol:host:port, where protocol is the communications protocol (beginning with ssl: for SSL, or tcp: for plaintext), host is the name of the machine on which p4d is running, and port is the number of the port on which p4d is listening. For example:

P4PORT	Behavior
tcp:server1:3435	Helix Core Server applications connect in plaintext to the Helix Core Server on host server1 listening on port 3435.
tcp64:server1:3435	Helix Core Server applications connect in plaintext to the Helix Core Server on host server1 listening on port 3435. The application first attempts to connect over an IPv6 connection; if that fails, the application attempts to connect via IPv4.
ssl:example.org:1818	Helix Core Server applications connect via SSL to the Helix Core Server on host example.org listening on port 1818.
<not set>	Helix Core Server applications connect to the Helix Core Server on a host named or aliased perforce listening on port 1666. Plaintext communications are assumed.

If you have enabled SSL, users are shown the server’s fingerprint the first time they attempt to connect to the service. If the fingerprint is accurate, users can use the p4 trust command (either p4 trust -y, or p4 -p ssl:host:port trust -i fingerprint) to install the fingerprint into a file (pointed to by the P4TRUST environment variable) that holds a list of known and trusted Helix Core Servers and their respective fingerprints. If P4TRUST is unset, this file is .p4trust in the user’s home directory.