Fix broken links

This commit is contained in:
Owen
2025-08-24 20:57:15 -07:00
parent d2ce282f9c
commit 155cae2efb
13 changed files with 19 additions and 19 deletions

View File

@@ -612,7 +612,7 @@ This section contains the complete reference for all configuration options in `c
**Example**: `postgresql://user:password@host:port/database`
<Note>
See [PostgreSQL documentation](../database/postgres) for setup instructions.
See [PostgreSQL documentation](/self-host/advanced/database-options#postgresql) for setup instructions.
</Note>
</ResponseField>
</Expandable>

View File

@@ -119,7 +119,7 @@ service:
<Warning>
Dockers NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
</Warning>
7. Verify communication between the firewall bouncer and the CrowdSec container by running:

View File

@@ -95,7 +95,7 @@ trusted_proxies:
- VPS IP
```
You also need to set up `Resource rules` in the pangolin dashboard. [See rule overview here](../03-Pangolin/05-bypass-rules.md).
You also need to set up `Resource rules` in the pangolin dashboard. [See rule overview here](/manage/access-control/bypass-rules).
Many thanks to steuerlexi for finding this out!

View File

@@ -30,7 +30,7 @@ service:
<Warning>
Dockers NAT-based port publishing feature automatically exposes all `ports:` defined in `docker-compose` file. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
</Warning>
2. Update the `/config/traefik/traefik_config.yml` file to include the following:
@@ -74,7 +74,7 @@ service:
<Warning>
Dockers NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
</Warning>
@@ -105,7 +105,7 @@ services:
<Warning>
Dockers NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
</Warning>
@@ -162,7 +162,7 @@ services:
<Warning>
Dockers NAT-based port publishing feature automatically exposes all `ports:` defined in the `docker-compose` file on all network interfaces. This behavior can bypass your host firewall settings, potentially exposing services that you did not intend to make public.
Please see [complete warning about exposing ports](/Getting%20Started/dns-networking#ports-to-expose).
Please see [complete warning about exposing ports](/self-host/dns-and-networking).
</Warning>
2. Start the Grafana container:

View File

@@ -4,7 +4,7 @@ description: "Learn how to convert your self-hosted Pangolin instance to a manag
---
<Info>
Check out the [Managed Deployment Guide](/self-host/managed-deployment) for more information on deploying a managed instance of Pangolin.
Check out the [Managed Deployment Guide](/self-host/quick-install-managed) for more information on deploying a managed instance of Pangolin.
</Info>
## Who is this for?

View File

@@ -39,7 +39,7 @@ Files marked with `(*)` must be created manually. Volumes and other files are ge
<Accordion title="Configuration Files">
**`config/config.yml`**: Main Pangolin configuration file
- Contains all Pangolin settings and options
- See [Configuration Guide](/pangolin/configuration/config) for details
- See [Configuration Guide](/self-host/advanced/config-file) for details
**`config/traefik/traefik_config.yml`**: Traefik static configuration
- Global Traefik settings and entry points

View File

@@ -4,7 +4,7 @@ description: "Deploy managed Pangolin manually using Docker Compose without the
---
<Tip>
This guide is for managed Pangolin. If you are looking for self-hosted Pangolin please see the [Docker Compose](self-host/docker-compose) guide.
This guide is for managed Pangolin. If you are looking for self-hosted Pangolin please see the [Docker Compose](/self-host/manual/docker-compose) guide.
</Tip>
This guide walks you through setting up Pangolin manually using Docker Compose without the automated installer. This approach gives you full control over the configuration and deployment process.
@@ -39,7 +39,7 @@ Files marked with `(*)` must be created manually. Volumes and other files are ge
<Accordion title="Configuration Files">
**`config/config.yml`**: Main Pangolin configuration file
- Contains all Pangolin settings and options
- See [Configuration Guide](/pangolin/configuration/config) for details
- See [Configuration Guide](/self-host/advanced/config-file) for details
**`config/traefik/traefik_config.yml`**: Traefik static configuration
- Global Traefik settings and entry points

View File

@@ -46,7 +46,7 @@ Pangolin uses a yaml file for configuration. If this is not present on start up,
Create a `config.yml` file in the `config` folder.
See the [Configuration](/pangolin/configuration/config) section for what to put in this file.
See the [Configuration](/self-host/advanced/config-file) section for what to put in this file.
```
pangolin/