Network Requirements for JFrog Products
Artifactory, Xray, and other JFrog products all need to be set with static IP addresses.
Artifactory, Xray, and other JFrog products all need to be set with static IP addresses. These services also need to be able to communicate directly with each other over the same LAN connection. Hosting these services in geographically distant locations may cause health checks to temporarily fail. Ensure the ports are open and no firewalls block communications between these services.
Shared Internal Network
All JFrog products in a JFrog Platform Deployment (JPD) must share the same internal network. To ensure this, do one of the following:
- Install all products in the same Kubernetes cluster.
- Install all products on virtual machines (VMs) connected to a single LAN.
In a single JPD, do not mix JFrog products deployed in Kubernetes clusters with JFrog products deployed outside the cluster. Kubernetes environments typically use dynamic addressing and other features that can break communication between JFrog products.
Artifactory Network Ports
Artifactory uses external network ports to communicate with services outside Artifactory and internal network ports to communicate with Artifactory and other JFrog Platform microservices.
External Network Ports
Artifactory uses the following external network ports by default:
- 8081
- 8082
Internal Network Ports
Artifactory uses the following internal network ports.
Microservice | Port |
|---|---|
Artifactory | HTTP: 8081, 8091 |
Frontend | HTTP: 8070 |
Access | HTTP: 8040, 8015 gRPC: 8045, 8016 |
Topology | HTTP: 8020 gRPC: 8021 |
One Model | HTTP: 8071 gRPC: 8072 |
Apollo Router | HTTP: 8074 |
Metadata | HTTP: 8086 |
Router | HTTP: 8082, 8046, 8049 gRPC: 8047 |
Observability | HTTP: 8036 gRPC: 8037 |
Event | HTTP:8061 gRPC: 8062 |
Mission Control | HTTP: 8080 |
JFConnect | HTTP: 8030 gRPC: 8035 |
JFConfig | HTTP: 8010 |
Evidence | HTTP: 8051 |
Artifactory Federation Service (RTFS) | HTTP: 8025 gRPC: 8026 |
Updated 5 days ago
