vh/NetAlertX
1
0
Fork 0
mirror of https://github.com/jokob-sk/NetAlertX.git synced 2026-04-05 17:51:25 -07:00
Code Issues Actions 6 Packages Projects Releases Wiki Activity

Fix NOTE and WARNING Formatting.

Browse Source
This commit is contained in:
luckylinux
2026-01-10 14:03:28 +01:00
parent 90b662ccb7
commit ab6e520fd6
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/REVERSE_PROXY.md
View File

@@ -568,7 +568,7 @@ The Traffic Flow will therefore be as follows:
- Authentik Outpost: Client accesses `https://authentik.MYDOMAIN.TLD:9443` -> reverse Proxy to internal Port 6000 (Authentik Outpost Proxy - unencrypted) - Authentik Outpost: Client accesses `https://authentik.MYDOMAIN.TLD:9443` -> reverse Proxy to internal Port 6000 (Authentik Outpost Proxy - unencrypted)
### Security Considerations ### Security Considerations
[!WARNING] > [!WARNING]
> By default Caddy runs as `root` which is a Security Risk. > By default Caddy runs as `root` which is a Security Risk.
> In order to solve this, it's recommended to create an unprivileged User `caddy` and Group `caddy` on the Host: > In order to solve this, it's recommended to create an unprivileged User `caddy` and Group `caddy` on the Host:
> ``` > ```
@@ -1131,7 +1131,7 @@ Wait a few Seconds for the Outpost to be created. Once it appears in the List, c
Take note of that Token. You will need it for the Authentik Outpost Proxy Container, which will read it as the `AUTHENTIK_TOKEN` Environment Variable. Take note of that Token. You will need it for the Authentik Outpost Proxy Container, which will read it as the `AUTHENTIK_TOKEN` Environment Variable.
### NGINX Configuration inside NetAlertX Container ### NGINX Configuration inside NetAlertX Container
[!NOTE] > [!NOTE]
> This is something that was implemented based on the previous Content of this Reverse Proxy Document. > This is something that was implemented based on the previous Content of this Reverse Proxy Document.
> Due to some Buffer Warnings/Errors in the Logs as well as some other Issues I was experiencing, I increased a lot the client_body_buffer_size and large_client_header_buffers Parameters, although these might not be required anymore. > Due to some Buffer Warnings/Errors in the Logs as well as some other Issues I was experiencing, I increased a lot the client_body_buffer_size and large_client_header_buffers Parameters, although these might not be required anymore.
> Further Testing might be required. > Further Testing might be required.