pangolin_mirror/docs-v2
1
0
Fork 0
mirror of https://github.com/fosrl/docs-v2.git synced 2026-08-31 03:01:30 +02:00
Code Issues Packages Projects Releases Wiki Activity

Update routing information

Browse Source
This commit is contained in:
Owen
2026-08-21 12:09:34 -04:00
parent afe66f5f90
commit 47bfc5763c
2 changed files with 21 additions and 17 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
manage/endpoints-and-pops.mdx
View File

@@ -4,10 +4,11 @@ icon: "network-wired"
description: "Pangolin Cloud hostnames for firewall allowlists and network whitelisting"
---
<Note>
This page applies to [Pangolin Cloud](https://app.pangolin.net/auth/signup) only. If you self-host Pangolin, see [DNS & Networking](/self-host/dns-and-networking) for the hostnames and ports on your own deployment.
This page applies to [Pangolin Cloud](https://app.pangolin.net/auth/signup)
only. If you self-host Pangolin, see [DNS &
Networking](/self-host/dns-and-networking) for the hostnames and ports on
your own deployment.
</Note>
Use this page when you need to allowlist Pangolin in a corporate firewall, proxy, or egress policy. Sites, clients, and browsers connect to two classes of infrastructure on Pangolin Cloud: the **control plane** and **points of presence** (also called relays).
@@ -16,8 +17,8 @@ Use this page when you need to allowlist Pangolin in a corporate firewall, proxy
The control plane is the central Pangolin service that runs the dashboard, REST API, authentication, and configuration orchestration.
| Hostname | Purpose |
| --- | --- |
| Hostname | Purpose |
| ------------------ | --------------------------------------------------------------------------------- |
| `app.pangolin.net` | Dashboard, API, authentication, and WebSocket configuration for sites and clients |
Sites and clients use this hostname as their **endpoint**. For example, Sites connect here to register, receive policy, and maintain their control channel.
@@ -26,17 +27,18 @@ Sites and clients use this hostname as their **endpoint**. For example, Sites co
Points of presence (PoPs), also called relays, are the networking edge where sites and clients connect for data traffic.
| Hostname |
| --- |
| `uranus.pop.pangolin.net` |
| `mars.pop.pangolin.net` |
| `earth.pop.pangolin.net` |
| `jupiter.pop.pangolin.net` |
| `saturn.pop.pangolin.net` |
| `neptune.pop.pangolin.net` |
| `pluto.pop.pangolin.net` |
| `mercury.pop.pangolin.net` |
| `erid.pop.pangolin.net` |
| Hostname | Location |
| -------------------------- | -------- |
| `jupiter.pop.pangolin.net` | US West |
| `saturn.pop.pangolin.net` | US West |
| `neptune.pop.pangolin.net` | US West |
| `earth.pop.pangolin.net` | US East |
| `mars.pop.pangolin.net` | US East |
| `erid.pop.pangolin.net` | US East |
| `pluto.pop.pangolin.net` | US East |
| `uranus.pop.pangolin.net` | Europe |
| `venus.pop.pangolin.net` | Europe |
| `mercury.pop.pangolin.net` | Europe |
### What PoPs Do

4
manage/resources/public/targets.mdx
View File

@@ -68,7 +68,7 @@ You can now configure targets across different sites for the same resource:
This is an [Enterprise Edition](/self-host/enterprise-edition)-only feature.
</Note>
This refers to having more than on Pangolin server node that a site can connect to. If one of the server nodes goes down, the site moves to another node. This has some implications for site-based load balancing, because DNS must can only route a FQDN to one Pangolin server node at a time.
On highly available clustered Enterprise Pangolin servers - lik the cloud platform - different sites can connect to different nodes. If one of the nodes goes down, the site moves to another node. This has implications for site-based load balancing, because DNS must can only route a FQDN to one Pangolin server node at a time.
Load balancing between different targets only works when sites are connected to the same Pangolin node. In Pangolin instances with multiple remote nodes, ensure load balancing occurs on the same node.
@@ -78,6 +78,8 @@ To ensure effective load balancing in multi-node environments:
newt --prefer-endpoint <specific-endpoint> <other-args>
```
For a list of endpoints used on the cloud platform, take a look at `/manage/endpoints-and-pops#points-of-presence`.
## Path-Based Routing
Path-based routing allows you to direct traffic to different targets based on the request path. This enables sophisticated routing scenarios where different services can handle different parts of your application.