IntenseWebs/LibreQoS
3
0 Fork 0
mirror of https://github.com/LibreQoE/LibreQoS.git synced 2026-10-31 08:34:04 -05:00
Code Issues Packages Projects Releases Wiki Activity

Fix API docs routing behind managed Caddy HTTPS

Browse Source
This commit is contained in:
Herbert Wolverson committed 2026-09-04 15:17:23 -05:00
1 parent 750560a14d
commit 87f0d595d7
5 files changed
+14 -6
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/v2.0/https-caddy.md
+5 -1
View File
@@ -21,7 +21,11 @@ LibreQoS supports two simple choices:
- LibreQoS moves the WebUI listener to `127.0.0.1:9123`.
- Caddy proxies the WebUI and API docs over HTTPS.
- Managed Caddy mode proxies API requests to `127.0.0.1:9122`, so the API stays behind the same HTTPS origin as the WebUI.
- Swagger moves to `/api/v1/api-docs` on the same HTTPS origin as the WebUI.
- Swagger moves to `/api-docs/` on the same HTTPS origin as the WebUI.
The API documentation is public; API requests still require an API key. Existing `/api/v1/api-docs` links redirect to `/api-docs/`.
After upgrading an existing HTTPS installation, reapply your settings in `Configuration -> SSL Setup` to update the Caddy routes. This regenerates `/etc/caddy/Caddyfile`, replacing manual edits, and restarts Caddy, the WebUI, and the API service.
## API Listen Overrides