update references from newt to pangolin site

This commit is contained in:
miloschwartz
2026-09-16 11:39:30 -04:00
parent 122f06f95a
commit 2f05e10c5d
23 changed files with 470 additions and 118 deletions
+1 -1
View File
@@ -133,7 +133,7 @@ After making these changes, restart both Traefik and Pangolin for the configurat
### Troubleshooting
If websockets are not connecting like from newt or clients, ensure that websockets are enabled in Cloudflare:
If websockets are not connecting from sites or clients, ensure that websockets are enabled in Cloudflare:
<Frame>
<img src="/images/cf_websocket_box.png" alt="Cloudflare dashboard WebSockets setting toggled on" width="600" centered/>
+1 -1
View File
@@ -233,7 +233,7 @@ If Pangolin can't reach the local Gerbil at the address in `--reachableAt` (a lo
</Step>
<Step title="Write config.yml">
`config.yml` holds the settings that legitimately differ per node - `gerbil.base_endpoint` and `gerbil.exit_node_name` - alongside the shared PostgreSQL connection and site-type restrictions. In clustered deployments, only Newt sites are supported, so local and basic WireGuard sites are disabled.
`config.yml` holds the settings that legitimately differ per node - `gerbil.base_endpoint` and `gerbil.exit_node_name` - alongside the shared PostgreSQL connection and site-type restrictions. In clustered deployments, only Pangolin Sites are supported, so local and basic WireGuard sites are disabled.
Set `app.dashboard_url` and `server.cors.origins` to your dashboard domain (the one pointed at your load balancer, not at either node) - both must match on every node.
+1 -1
View File
@@ -103,7 +103,7 @@ dns:
- **Contact email** for Let's Encrypt ACME registration
- **GeoIP databases** - download and keep up to date the MaxMind `GeoLite2-Country.mmdb` and `GeoLite2-ASN.mmdb` databases, placed in each node's `config/` directory. See [Enable Geo-location](/self-host/advanced/enable-geolocation) and [Enable ASN Lookup](/self-host/advanced/enable-asn-lookup)
- **Site type support** - in clustered deployments, only Newt sites are supported. Local sites and basic WireGuard sites are not supported
- **Site type support** - in clustered deployments, only Pangolin Sites are supported. Local sites and basic WireGuard sites are not supported
<Card title="Deploy a Cluster" href="/self-host/clustering/deploy-a-cluster" icon="server">
Once these requirements are met, follow the full deployment walkthrough.
@@ -76,7 +76,7 @@ A Pangolin cluster consists of several coordinated components that work together
**How It Works**:
- Each Pangolin instance runs alongside its own Gerbil tunnel manager
- Handles WireGuard VPN connections from site connectors (Newt)
- Handles WireGuard VPN connections from Pangolin Site connectors
- Site connectors can establish tunnels to any available Gerbil instance
- Every Gerbil instance is made aware of the other trusted nodes in the cluster
- When a request lands on the node that isn't holding the relevant tunnel, Gerbil routes it to the correct node instead of dropping it - this covers the case where DNS caching sends a client to the "wrong" node
+2 -2
View File
@@ -77,13 +77,13 @@ Pangolin requires these ports to be open on your VPS:
<Card title="UDP Port 51820">
**Site Tunnels**
This is the default port for sites (Newt) to establish tunnels to the proxy (Gerbil).
This is the default port for Pangolin Sites to establish tunnels to the proxy.
</Card>
<Card title="UDP Port 21820">
**Client Tunnels**
This is the default port for clients relaying through Gerbil to newt. This port is only required for clients.
This is the default port for clients relaying through the server to Pangolin Sites. This port is only required for clients.
</Card>
</CardGroup>
@@ -888,7 +888,7 @@ pangolin:
```
<Warning>
The Pangolin server does not apply Blueprint files directly. Blueprints are applied by Newt through the Pangolin API using `--blueprint-file` or `--provisioning-blueprint-file`.
The Pangolin server does not apply Blueprint files directly. Blueprints are applied by Pangolin Sites through the Pangolin API using `--blueprint-file` or `--provisioning-blueprint-file`.
</Warning>
</Accordion>