To allow users access to Helix TeamHub via Web browsers and version control clients, make sure Helix TeamHub 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 will be used).
If Helix TeamHub LDAP interface is enabled, the following connections are required:
TCP 389- Unencrypted LDAP connection.
TCP 636- Encrypted LDAPS connection (only if SSL will be used).
TCP 4002from Helix TeamHub Web to Helix TeamHub DB server - Access to MongoDB database.
TCP 6379from Helix TeamHub Web to Helix TeamHub DB server - Access to Redis database.
For convenience, it's recommended the user check arrows and corresponding ports for deployment type, and then reference here for a more detailed explanation of the port usage.
Helix TeamHub may use a number of external services for mailing, authentication, etc. If external services are required, make sure the following connections are open for Helix TeamHub servers to access: