alvis/AgapHost
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

caddy: add dl.alogins.net for ad-hoc file sharing

agap-mcp
2026-05-26 13:17:53 +00:00
parent f1717b1eee
commit 9778392594
1 changed files with 15 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
Network.md

@@ -65,6 +65,17 @@ openpi.alogins.net {
file_server browse file_server browse
} }
# Ad-hoc file sharing — explicit per-file path mapping, no directory listing
dl.alogins.net {
@chiefx8 path /chief-x8.zip
handle @chiefx8 {
root * /mnt/misc/qbittorrent/downloads
rewrite * "/Chief Architect Premier X8 18.1.1.4 Portable.zip"
file_server
}
respond 404
}
# VPN proxy (3X-UI) # VPN proxy (3X-UI)
vui3.alogins.net { vui3.alogins.net {
@xhttp { path /VLSpdG9k/xht* } @xhttp { path /VLSpdG9k/xht* }
@@ -100,6 +111,10 @@ sudo systemctl enable --now caddy
**HTTP/3 disabled globally** — the top-level `protocols h1 h2` option forces HTTP/1.1 and HTTP/2 only. OnlyOffice editor assets stall over HTTP/3 on distant connections (Caddy aborts with `writing: timeout: no recent network activity`), which breaks the Seafile → OnlyOffice flow. HTTP/2 handles the same payloads without issue. **HTTP/3 disabled globally** — the top-level `protocols h1 h2` option forces HTTP/1.1 and HTTP/2 only. OnlyOffice editor assets stall over HTTP/3 on distant connections (Caddy aborts with `writing: timeout: no recent network activity`), which breaks the Seafile → OnlyOffice flow. HTTP/2 handles the same payloads without issue.
### Ad-hoc file sharing pattern
Use `dl.alogins.net` for temporary public downloads. Map each file to an explicit short path inside a `handle` block; default to `respond 404` so the host does not leak structure. Caddy runs as the `caddy` user — make sure the file is world-readable (`chmod o+r`) or accessible to that user. Remove the `handle` block when no longer needed.
### Hairpin NAT ### Hairpin NAT
The router does not support hairpin NAT — the server cannot reach its own public IP from within the LAN. Services that need to call back to a public domain from the host or from Docker containers must use local overrides. The router does not support hairpin NAT — the server cannot reach its own public IP from within the LAN. Services that need to call back to a public domain from the host or from Docker containers must use local overrides.