6.2.3 Nodes Port Configuration
As a result of installing the node in given containers, several services are launched, the ports of which are presented in the table below. Open ports can be checked with the sudo ss -ltn command.
# | TCP/IP Port | Service | External Usage |
1 | 22 | SSH service, required for remote access to the server | Required for remote interaction with the node |
2 | 4104 | The service of the main component – the validator and interaction with the transaction processor (including support for internal rest-API) | Must be open if the dashboard is located on a different physical machine |
3 | 5051 | Port for other components to interact with the consensus service (for Inner net) |
|
4 | 8003 | Rest-Api Dashboard | Must be opened if the service is located on a separate server or outside the Inner-net network |
5 | 8101 | Node interaction | Must be open for interacting with other nodes |
6 | 8108 | Node interaction | Must be open if the node will accept external requests to execute transactions |
DGT nodes can use various network ports for communication, which are configured through environment variables set up by the upDgtCluster.sh script in the DGT director (for example, /DGT-Matagami/CORE):
- API=8108 (API service)
- COMP=4104 (supporting transaction families)
- NET=8101 (supporting the network)
- CONS=5051 (consensus service)
Last updated
