haylan/LLM-Server
1
0
Fork 0
Code Issues 9 Pull Requests Actions Packages Projects Releases Wiki Activity

Network/hostname plan for exposing the proxy (LAN + external) #13

New Issue
Closed
opened 2026-08-25 04:39:56 +00:00 by haylan · 1 comment
haylan commented 2026-08-25 04:39:56 +00:00
Owner
Copy Link
Copy Source

Part of #9

Question

Per #9's Notes, the proxy needs to be reachable LAN + external, mirroring Open WebUI's ai.home / ai.haylan.ch pattern via the existing NPM instance (see docs/network-access.md). What's the concrete plan: hostname(s), whether it shares Open WebUI's domain or gets its own subdomain, auth exposure concerns now that llama.cpp's raw (currently LAN-only, unauthenticated) API sits behind it, and any changes needed to llama.cpp's own network posture from map #1.

Part of #9 ## Question Per #9's Notes, the proxy needs to be reachable LAN + external, mirroring Open WebUI's ai.home / ai.haylan.ch pattern via the existing NPM instance (see docs/network-access.md). What's the concrete plan: hostname(s), whether it shares Open WebUI's domain or gets its own subdomain, auth exposure concerns now that llama.cpp's raw (currently LAN-only, unauthenticated) API sits behind it, and any changes needed to llama.cpp's own network posture from map #1.
haylan added the wayfinder:grilling label 2026-08-25 04:39:56 +00:00
haylan added a new dependency 2026-08-25 04:40:15 +00:00
#14 Author the docker-compose service for the chosen proxy
haylan self-assigned this 2026-08-25 04:58:05 +00:00
haylan commented 2026-08-25 05:05:08 +00:00
Author
Owner
Copy Link
Copy Source

Resolved via grilling.

Hostnames: proxy.ai.home (LAN) / proxy.ai.haylan.ch (external) — new NPM Proxy Hosts, same pattern as Open WebUI's ai.home/ai.haylan.ch. LiteLLM's own virtual-key auth (per #12) is sufficient for external exposure — no extra NPM-level auth layer. LiteLLM's Admin UI (/ui) stays LAN-only, reachable only via proxy.ai.home — since it shares a port with the API by default, the external proxy.ai.haylan.ch NPM host needs an explicit rule denying the /ui path.

Documented in docs/network-access.md, committed on main.

Resolved via grilling. Hostnames: **proxy.ai.home** (LAN) / **proxy.ai.haylan.ch** (external) — new NPM Proxy Hosts, same pattern as Open WebUI's ai.home/ai.haylan.ch. LiteLLM's own virtual-key auth (per #12) is sufficient for external exposure — no extra NPM-level auth layer. LiteLLM's Admin UI (/ui) stays LAN-only, reachable only via proxy.ai.home — since it shares a port with the API by default, the external proxy.ai.haylan.ch NPM host needs an explicit rule denying the /ui path. Documented in docs/network-access.md, committed on main.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
wayfinder:grilling
Wayfinder grilling ticket
 wayfinder:map
Wayfinder map issue
 wayfinder:prototype
Wayfinder prototype ticket
 wayfinder:research
Wayfinder research ticket
 wayfinder:task
Wayfinder task ticket
No labels wayfinder:grilling
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
haylan (Arthur Erlich)
No Assignees haylan
1 Participants
Notifications
Due Date
No due date set.
Blocks
#14 Author the docker-compose service for the chosen proxy
haylan/LLM-Server
Reference: haylan/LLM-Server#13