Skip to content

Commit 2893790

Browse files
Joanna-Sessiongitbook-bot
authored andcommitted
GITBOOK-157: No subject
1 parent 044a10a commit 2893790

File tree

1 file changed

+8
-3
lines changed
  • contribute-to-the-session-network/running-a-session-node

1 file changed

+8
-3
lines changed

contribute-to-the-session-network/running-a-session-node/README.md

Lines changed: 8 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -123,10 +123,13 @@ Alright, good to go. Our server is now set up, up to date, and is not running as
123123

124124
#### 2.3: Firewall configuration
125125

126-
If you are using a firewall then ensure that the following ports are open/reachable
126+
If you are using a firewall then you should ensure that the following ports are open and reachable:
127127

128-
* Port 22022 (blockchain syncing)
129-
* Port 22025 (Session Node to Session Node)
128+
* 22020 (Storage Server to Storage Server, TCP & UDP)
129+
* 22021 (Session Client to Storage Server, TCP)
130+
* 22022 (Blockchain syncing, TCP)
131+
* 22025 (Session Node to Session Node, TCP)
132+
* 1090 (Lokinet router data, UDP)
130133

131134
### Step 3: Initial repository setup
132135

@@ -341,6 +344,8 @@ Use the [My Stakes](https://stake.getsession.org/mystakes) page to monitor the s
341344

342345
> **Note:** If you're staking vesting SESH, you'll need to **switch off** Vesting Mode first to be able to see your rewards. 
343346
347+
You can also verify that the Storage Server is reachable over UDP using [quictest.oxen.io](https://quictest.oxen.io/) once the Session Node is registered onto the network successfully as part of monitoring your node.
348+
344349
### Back-ups
345350

346351
You should immediately make a backup of your Session Node's secret keys. This will allow you to migrate your node to a different hardware provider if necessary in the future.

0 commit comments

Comments
 (0)