Ports used by the Radix Node

Introduction

The Radix setup handles allocating ports during the node installation. If you are running on a cloud service, or your own secured server, then you need to ensure the required ports are open and available for use.

Ports used for the Radix Node

port number name node type public description

30000

Gossip port

full, validator, archive

yes

This is the port used by the nodes to communicate, so should always be available.

3333

Node HTTP REST endpoints

full, validator, archive

no

With the node REST API you can control some sensitive operations on the node, so this should be protected and not accessible by anyone that does not have node management privileges.

8080

Radix Node API endpoints

archive

yes

If you decide to run an archive node, then this port needs to be accessible publicly.

Nginx Ports

In order to protect the node we use Nginx to provide URLs that don’t expose the node services directly. A well as hiding the node endpoints, the Nginx provides three other functions:

  1. It adds basic authentication to the endpoints that should only be available to node administrators/managers.

  2. Provides rate limiting to provide a basic mechanism for Denial-of-Service protection

  3. Basic request caching

nginx port number nginx endpoint maps to Radix node port:

443

/rpc

8080

/universe.json

3333

/system

3333

/node

3333

30000

30000