# 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.

<figure><img src="https://3210145376-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FSvanFNAf6Jf8kwvqcdRQ%2Fuploads%2FAHZT5BYhuKLRdQBQTQo0%2Fimage.png?alt=media&#x26;token=84488990-9301-40c3-912b-3956fbfddc85" alt=""><figcaption><p><em>Figure 114 Opened ports after the dgt node building procedure</em></p></figcaption></figure>

<table data-header-hidden data-full-width="false"><thead><tr><th width="77.25"></th><th width="154"></th><th width="298"></th><th></th></tr></thead><tbody><tr><td><p> </p><p>#</p></td><td>TCP/IP Port</td><td>Service</td><td>External Usage</td></tr><tr><td>1</td><td>22</td><td>SSH service, required for remote access to the server</td><td>Required for remote interaction with the node</td></tr><tr><td>2</td><td>4104</td><td>The service of the main component – the validator and interaction with the transaction processor (including support for internal rest-API)</td><td>Must be open if the dashboard is located on a different physical machine</td></tr><tr><td>3</td><td>5051</td><td>Port for other components to interact with the consensus service (for Inner net)</td><td> </td></tr><tr><td>4</td><td>8003</td><td>Rest-Api Dashboard</td><td>Must be opened if the service is located on a separate server or outside the Inner-net network</td></tr><tr><td>5</td><td>8101</td><td>Node interaction</td><td>Must be open for interacting with other nodes</td></tr><tr><td>6</td><td>8108</td><td>Node interaction</td><td>Must be open if the node will accept external requests to execute transactions</td></tr></tbody></table>

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)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://dgtnetwork.gitbook.io/dgt-docs/6.-administrator-guide/6.2-dgt-core-single-node-setup/6.2.3-nodes-port-configuration.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.