Skip to main content
To ensure stable communication between VMS Master and VMS Agents, infrastructure and operations teams must configure the firewall rules to permit traffic on the following network ports.

​
Firewall Rules Table

SourceDestinationPortsDescription & Purpose
Customer server (Agent)VMS Server31082, 443, 31080, 31081API Port for agents to push metrics/logs and fetch configurations
VMS ServerInternet80, 443Outbound internet access to deploy K8s/K3s and pull docker images from GitLab
Jump/VPNVMS Server31082, 443, 31080, 31081, 22, 16443, 6443Access VMS Server for administration, management, and deployment
Port 31082 replaces the default HTTP port 80 to enhance security.

​
Troubleshooting Connectivity Issues

If you encounter connection drops, handshake failures, or timeout errors, perform the following verification steps:

​
1. Verification from the Agent side (Customer Server)

Check reachability to the Ingress HTTPS endpoint: 
# Test connection to the Ingress HTTPS API
curl -k https://ingest.vms.verolabs.co/healthz

​
2. Verification from the Master Server side

Verify that services and Ingress/NodePorts are listening properly on the designated ports: 
kubectl get svc -n vms