Port Forwarding & Firewall
Overview
This guide explains how to configure network settings and set up port forwarding for Autonomys Network. Correct port forwarding is essential to ensure proper communication between your node, farmer, and the Autonomys Network.
By opening specific ports on your router, you allow external traffic to reach your node, which is necessary for blockchain synchronization, data exchange, and remote procedure calls (RPC).
Additionally, you may need to adjust your system's firewall settings to allow traffic through the specified ports. Firewalls typically block unsolicited incoming connections, so it's important to ensure that the required ports are open. These adjustments will enable effective communication with the Autonomy Network.
Ports to Forward & Firewall Access
Ensure each node on the same network runs on unique ports. Adjust the ports mentioned in this guide if using multiple nodes or if default ports have been changed.
For security reasons, RPC ports 9944 and 9945 should never be exposed unless you intend to operate a public RPC server, and they should never be exposed on a system that is running a farmer or an operator.
- Space Acres
- Advanced CLI (Farmer)
- Advanced CLI (Domain Operator)
- RPC Server (Public)
Port | Protocol | ↪️ | 🛡️ | Component | Purpose |
---|---|---|---|---|---|
30333 | TCP | ☑️ | ☑️ | Node (Consensus) | Facilitate block, transaction, and PoT gossip exchange. |
30433 | TCP | ☑️ | ☑️ | Node (DSN) | Retrieve and serve pieces of data and metadata related to archival history from the P2P network. |
Port | Protocol | ↪️ | 🛡️ | Component | Purpose |
---|---|---|---|---|---|
30333 | TCP | ☑️ | ☑️ | Node (Consensus) | Facilitate block, transaction, and PoT gossip exchange. |
30433 | TCP | ☑️ | ☑️ | Node (DSN) | Retrieve and serve pieces of data and metadata related to archival history from the P2P network. |
30533 | TCP | ☑️ | ☑️ | Farmer | Retrieve blockchain archival history. |
9944 | TCP | ❌ | ☑️ | Node (Consensus RPC) | Required for farmer operation. |
Port | Protocol | ↪️ | 🛡️ | Component | Purpose |
---|---|---|---|---|---|
30333 | TCP | ☑️ | ☑️ | Node (Consensus) | Facilitate block, transaction, and PoT gossip exchange. |
30334 | TCP | ☑️ | ☑️ | Node (Domain) | Essential for a domain node to maintain strong connectivity with the P2P network. |
30433 | TCP | ☑️ | ☑️ | Node (DSN) | Retrieve and serve pieces of data and metadata related to archival history from the P2P network. |
Port | Protocol | ↪️ | 🛡️ | Component | Purpose |
---|---|---|---|---|---|
9944 | TCP | ☑️ | ☑️ | Node (Consensus RPC) | Enables transaction submissions via HTTP and WebSocket, supports slot challenges, and provides access to real-time and historical blockchain data for querying events, transactions, block contents, and chain state. |
9945 | TCP | ☑️ |