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

Fix broken links

Browse Source
This commit is contained in:
Owen
2025-11-08 14:34:53 -08:00
parent 28c8b8845e
commit 8a34ecebe8
4 changed files with 5 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
about/how-pangolin-works.mdx
View File

@@ -40,13 +40,9 @@ Pangolin provides secure, application-specific ingress to your applications thro
Fully self-hosted, self-contained Pangolin server acting as a single node.
</Card>
<Card title="Remote Nodes" icon="circle-nodes" href="/manage/remote">
<Card title="Remote Nodes" icon="circle-nodes" href="/manage/remote-node/ha">
Self-host your own Pangolin node with cloud coordination for high availability and automatic failover. Data always transits your servers.
</Card>
<Card title="Learn More" icon="book" href="/manage/nodes">
Detailed information about nodes and high availability options.
</Card>
</CardGroup>
## Key Benefits

4
manage/clients/add-client.mdx
View File

@@ -115,7 +115,7 @@ Sites have two operating modalities when accepting clients:
### Proxy Mode
When you run Newt with `--accept-clients` it will run fully in user space. This means you do not need to give the container or binary any special permissions. It will NOT create a virtual network interface on the host. Instead you should create [client resources](/resources/client-resources) in Pangolin to configure what ports clients can hit and where they should go.
When you run Newt with `--accept-clients` it will run fully in user space. This means you do not need to give the container or binary any special permissions. It will NOT create a virtual network interface on the host. Instead you should create [client resources](/manage/resources/client-resources) in Pangolin to configure what ports clients can hit and where they should go.
### Native Mode
@@ -164,7 +164,7 @@ If you can connect to Newt (peer shows as connected in logs) but can't reach rem
1. **Check if packets reach the destination**: The connection to Newt is working, so this is likely a routing issue
2. **Verify forwarding is enabled**: Use `sysctl net.ipv4.ip_forward` to confirm it's set to 1
3. **Check iptables rules**: Ensure NAT masquerading is configured
4. **Consider using proxy mode**: [Client resources](/resources/client-resources) can be easier as Newt handles the proxying, though you'll need to address everything as the Newt IP and assign specific ports
4. **Consider using proxy mode**: [Client resources](/manage/resources/client-resources) can be easier as Newt handles the proxying, though you'll need to address everything as the Newt IP and assign specific ports
<Note>
NAT masquerading can affect other services on the Linux instance, so be aware of potential conflicts with existing network configurations.

2
manage/healthchecks-failover.mdx
View File

@@ -14,7 +14,7 @@ description: "Configure automated health monitoring and failover for high availa
## Overview
Pangolin provides automated health checking for [targets](/resources/targets) to ensure traffic is only routed to healthy services. Health checks are essential for building highly available services, as they automatically remove unhealthy targets from traffic routing and load balancing.
Pangolin provides automated health checking for [targets](/manage/resources/targets) to ensure traffic is only routed to healthy services. Health checks are essential for building highly available services, as they automatically remove unhealthy targets from traffic routing and load balancing.
## How Health Checks Work

2
manage/resources/client-resources.mdx
View File

@@ -5,7 +5,7 @@ description: "Configure resources for Olm clients to access on a Newt site"
## Overview
Site resources in Pangolin allow you to define specific ports and a destination that can be accessed through the VPN tunnel when using [Olm clients](/clients/add-client). This is useful for exposing internal services to your remote clients securely.
Site resources in Pangolin allow you to define specific ports and a destination that can be accessed through the VPN tunnel when using [Olm clients](/manage/clients/add-client). This is useful for exposing internal services to your remote clients securely.
<Note>
Site resources are only for exposing services on a Newt site to Olm clients running remotely and do not get proxied.