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: README.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -51,7 +51,7 @@
51
51
52
52
## Key Concepts
53
53
54
-
-**GATEWAY** – a Linux-based machine with Docker installed, a public IP address, and the following open ports: 80/tcp, 443/tcp, 4060/tcp, 51820/udp and 32420-32430/tcp+udp. This node acts as the ingress gateway and an entry point to your published services.
54
+
-**GATEWAY** – a Linux-based machine with Docker installed, a public IP address, and the following open ports: 80/tcp, 443/tcp, 4060/tcp, 51820/udp and 32420-32421/tcp+udp. This node acts as the ingress gateway and an entry point to your published services.
55
55
-**CLIENT** – any number of laptops/PCs that will connect to the WireGuard network to manage the ingress network and expose services from their local machines to the Internet.
56
56
-**SERVER***(optional)* – one or more Linux-based machines (with Docker) that run the workloads you want to expose. These nodes join the same private WireGuard network, provided by the GATEWAY.
Copy file name to clipboardExpand all lines: app/cmd/server/main.go
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ var rootCmd = &cobra.Command{
20
20
21
21
Key Concepts:
22
22
23
-
- GATEWAY – a Linux-based machine with Docker installed, a public IP address, and the following open ports: 80/tcp, 443/tcp, 4060/tcp, 51820/udp and, optionally, 32420-32430/tcp+udp. This node acts as the ingress gateway and an entry point to your published services.
23
+
- GATEWAY – a Linux-based machine with Docker installed, a public IP address, and the following open ports: 80/tcp, 443/tcp, 4060/tcp, 51820/udp and, optionally, 32420-32421/tcp+udp. This node acts as the ingress gateway and an entry point to your published services.
24
24
- CLIENT – any number of laptops/PCs that will connect to the WireGuard network to manage the ingress network and expose services.
25
25
- SERVER (optional) – one or more Linux-based machines (with Docker) that run the workloads you want to expose. These nodes join the same private WireGuard network, provided by the GATEWAY.
26
26
@@ -47,7 +47,7 @@ Now you should be able to access the Docker-based services from your local machi
47
47
48
48
If the installation process fails, or the service is not accessible over the Internet, make sure that:
49
49
50
-
- the required ports are open on the gateway VPS (80/tcp, 443/tcp, 4060/tcp, 51820/udp and, optionally, 32420-32430/tcp+udp)
50
+
- the required ports are open on the gateway VPS (80/tcp, 443/tcp, 4060/tcp, 51820/udp and, optionally, 32420-32421/tcp+udp)
51
51
- there's a correct DNS A-record, pointing to your gateway VPS
52
52
- the gateway VPS has docker installed
53
53
- the ssh user, used for bootstraping the gateway VPS, is allowed to run docker commands on the gateway VPS
0 commit comments