Hosts and ports

This page records the addresses of the project's environments and the ports used by each component. It is the only page in this documentation that contains host addresses.

When an environment moves to different machines, only this page requires updating. All other pages refer to machines by role.

Machine roles

Application host. Runs the Metadata application, the ETL service, the P2P nodes, and Keycloak.

Data host. Runs the shared PostgreSQL database and the MQTT message broker.

In a standalone deployment both roles are filled by the same machine.

Current environment

Verified 11 October 2026. These addresses are expected to change; confirm them before relying on them.

Role Address Hostname
Application host 10.222.30.212 cvdlink-vm1a
Data host 10.222.30.213 cvdlink-vm2b

Ports

Port assignments are fixed in the component images and configuration files, and do not change between environments.

Application host

Port Component Protocol Notes
48000 Metadata HTTP Published from container port 8000
8002 ETL HTTP API and interactive documentation
8060 P2P HTTP Node API
4447 P2P TCP Gossip protocol, published from container port 4444
8468 P2P UDP Peer discovery
7078 Keycloak HTTP Published from container port 8080
5444 PostgreSQL TCP Bundled instance, see below

Where several P2P nodes run on one machine for testing, each additional node uses the next available port in each range. The current environment runs three nodes on 8060/8061/8062, 4447/4445/4446, and 8468/8469/8470 respectively.

Data host

Port Component Protocol Notes
5432 PostgreSQL TCP Shared database, includes the pgvector extension
1883 MQTT broker TCP Node status events
9001 MQTT broker TCP WebSocket listener

The two PostgreSQL instances

The project operates two PostgreSQL instances with different purposes. They are not alternatives to one another.

Shared database, port 5432 on the data host. Built from the pgvector/pgvector:pg17 image and used by central deployments. Holds the cvdlink database together with additional databases used by other services. The pgvector extension is required by the assistant features.

Bundled database, port 5444. Installed as part of a standalone deployment, on the same machine as the applications, and restored automatically from a supplied dump at first start. It must be built from the same pgvector/pgvector:pg17 image, because the metadata schema requires the vector extension.

Two further port numbers appear in older configuration files and should be disregarded: 5492, a stale default in the ETL image, and 5433, which is not used in any current deployment.

External services

Service Address Purpose
Keycloak realm cvdlink.simavi.ro, realm cvdlink Authentication for central deployments
Documentation site Application host, port 8282 This documentation

Firewall requirements

For a central deployment, the application host requires outbound access to the data host on ports 5432 and 1883, and outbound HTTPS access to the Keycloak realm. Inbound access to port 48000 is required from client machines, or from the reverse proxy where one is used.

For federation, the P2P ports must be reachable in both directions between participating sites: TCP 4447 and UDP 8468.

A standalone deployment requires no inbound or outbound access beyond the client machines reaching port 48000.