This page lists the ports that are required for
...
Vera. These ports are configurable when installing
...
Vera, but examples are given below.
You must open these ports prior to installing
VERAVera.
The Server-to-Server ports listed below must be accessible between servers.
- Both the VERA Web Portal and VERA Server
These containers must be able to access the MongoDB database
. - The Client ports must be accessible by any user PC accessing VERA.
Server-to-Server Ports
...
Client Ports
...
vera-server
vera.worker.qtest
vera-web-portal
Service Name | Container Name | Port, Ext | Port, Int | Expose | Depends On | Health Probe | Purpose |
|---|---|---|---|---|---|---|---|
rabbitmq | rabbitmq | 15672 | 5672 | Message broker | |||
vera.server | vera-server | 8080 | 5000 | /rest | Legacy Vera Server components that have not migrated to microservices (replaces tx3/Vera-server) | ||
vera.worker.qtest | vera.worker.qtest | 80 | rabbitmq | /health/ready | Worker to handle qTest actions | ||
vera.api.qtest.routeactions | vera.api.qtest.routeactions | 5100 | 80 | vera.worker.qtest | /health/ready | Public API for Route Actions from qTest | |
vera.api.routes.routeevents | vera.api.routes.routeevents | 80 | vera.server | /health/ready | Internal API for Approval Events (Task Approved, Task Rejected, Route Completed) | ||
vera.api.connections.testconnection | vera.api.connections.testconnection | 80 | vera.server | Internal API to for connection tests | |||
vera.web.portal | vera-web-portal | 80 | 80 | /login | User Interface |