Required Ports
- HB Farris
- John Berek
URLs that were previously pointed to the Vera.Server container from qTest or Jira, will need to be repointed to the appropriate route actions container. Failure to do this will result in records not being routed for approval, withdrawn, or deleted correctly.
Example: A qTest project points to the following URL in the Vera Integration settings: https://client.vera.com/callbacks/qtest/route_action. Currently the url points to the Vera.Server container on port 8443. After upgrading to 2023.3, the URL will need to point to the Vera.Api.qTest.RouteActions container on port 6100. If the url cannot be re-routed via an application gateway or similar, then the url will need to be updated to point to the 6100 port manually. The same procedure will need to be followed for Jira URLs as well.
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 Vera.
The Server-to-Server ports listed below must be accessible between servers.
These containers must be able to access the MongoDB database
vera-server
vera.worker.qtest
vera-web-portal
vera.worker.jira
vera.worker.jobservice
vera.api.jira.routeactions
vera.api.routes.routeevents
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.worker.jira | vera.worker.jira |
|
| 80 443 | rabbitmq vera.worker.jobservice | /health/ready | Worker to handle Jira actions |
vera.api.jira.routeactions | vera.api.jira.routeactions | 5101 6101 | 80 443 |
| vera.worker.jira | /health/ready | Public API for Route Actions from jira |
vera.worker.jobservice | vera.worker.jobservice |
|
| 80 443 | rabbitmq | /health/ready | Worker to help with Jira requests |
vera.web.portal | vera-web-portal | 80 | 80 |
|
| /login | User Interface |