You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/networking.md
+8-10Lines changed: 8 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,12 +12,11 @@ Example for a node with public IP `1.2.3.4`, using ports 9000 (TCP) and 9001 (We
12
12
P2P_ANNOUNCE_ADDRESSES='[
13
13
"/ip4/1.2.3.4/tcp/9000",
14
14
"/ip4/1.2.3.4/tcp/9001/ws",
15
-
"/ip4/1.2.3.4/tcp/9001/tls/ws",
16
-
"/ip4/1.2.3.4/tcp/9001/tls/wss"
15
+
"/ip4/1.2.3.4/tcp/9001/tls/ws"
17
16
]'
18
17
```
19
18
20
-
The `/tls/ws`and `/tls/wss` entries enable [AutoTLS](#tls-and-sni-server-name-indication) for node-to-browser communication. AutoTLS handles certificate provisioning automatically — no DNS setup required on your part.
19
+
The `/tls/ws`entry enables [AutoTLS](#tls-and-sni-server-name-indication) for node-to-browser communication. AutoTLS provisions a certificate and serves TLS at the transport layer on the WebSocket port, making it browser-compatible — no DNS setup required on your part.
21
20
22
21
## Option 2: Dynamic DNS (no static IP)
23
22
@@ -31,8 +30,7 @@ Once you have a hostname (e.g. `mynode.duckdns.org`), set up the DDNS client on
31
30
P2P_ANNOUNCE_ADDRESSES='[
32
31
"/dns4/mynode.duckdns.org/tcp/9000",
33
32
"/dns4/mynode.duckdns.org/tcp/9001/ws",
34
-
"/dns4/mynode.duckdns.org/tcp/9001/tls/ws",
35
-
"/dns4/mynode.duckdns.org/tcp/9001/tls/wss"
33
+
"/dns4/mynode.duckdns.org/tcp/9001/tls/ws"
36
34
]'
37
35
```
38
36
@@ -74,16 +72,17 @@ Do not enable `P2P_ENABLE_CIRCUIT_RELAY_SERVER` on edge nodes; that setting is f
74
72
75
73
## TLS and SNI (Server Name Indication)
76
74
77
-
AutoTLS provisions TLS certificates for your node automatically, enabling P2P node-to-browser communication. It is always active internally — no DNS or certificate setup required on your part. For it to work, you must include `/tls/ws` or `/tls/wss` entries in `P2P_ANNOUNCE_ADDRESSES`, which the quickstart script does automatically.
75
+
AutoTLS provisions TLS certificates for your node automatically, enabling P2P node-to-browser communication. It is always active internally — no DNS or certificate setup required on your part. For it to work, you must include a `/tls/ws` entry in `P2P_ANNOUNCE_ADDRESSES`, which the quickstart script does automatically.
76
+
77
+
AutoTLS serves TLS at the transport layer on the WebSocket port, making it standard browser-compatible WSS — no separate port is needed.
0 commit comments