What You Get¶
A quick tour of the main pages. All screenshots use the default dark theme.
Dashboard¶

Dashboard - bandwidth saved, hit ratio, service analytics, and top clients in one view
Downloads¶

Downloads - every cached game with cover art, sizes, and per-client history
Four view modes: Compact, Card, Normal, and Retro. Hit and Miss, and the client filter, narrow the list.
Clients¶

Clients - which devices use the cache, and how well it serves each one
Open it when you want to know which machines pull the most and whether their installs hit the cache.
Users¶

Users - sessions, accounts and guest access
This is where guest access and signed-in accounts live: one list of sessions and accounts with a detail pane, Create account, and the Guest access entry, which hands out time-limited guest sessions and can grant Prefill per platform. The Sign-in entry sets how users sign in. The Primary account and its sessions are visible only to that account.
Events¶

Events - download activity and LAN events on a calendar
Add LAN parties to the calendar to see download activity by date.
Status Check¶

Status Check - verify DNS, cache reachability, and recent download routing
The Status Check tab (Management → Status Check) checks whether your LANCache is working, without a terminal. It checks that game domains resolve to your cache, that the cache answers, and that recent downloads really went through it - per domain, in plain language.
Why "From this device" cannot confirm the cache, and how to fix it
Your browser runs that one probe, not the server, so it reports what your client sees. It requests http://lancache.steamcontent.com/lancache-heartbeat, and a real cache node answers 204 with an X-LanCache-Processed-By header naming itself.
Browsers won't let a page read that header across origins unless the cache opts in. Current lancachenet/monolithic images have shipped that opt-in for years, so a definitive answer is the normal case. On an older image or a custom nginx config, the card falls back to a request that proves something answered but not what, reports that result, and logs a CORS error in your browser console. Nothing is broken. Every other Status Check result comes from the server and is unaffected.
To fix an older or custom cache, add these to the heartbeat location in its nginx config:
location /lancache-heartbeat {
add_header X-LanCache-Processed-By $hostname always;
add_header Access-Control-Allow-Origin "*" always;
add_header Access-Control-Expose-Headers "X-LanCache-Processed-By" always;
return 204;
}
Access-Control-Expose-Headers is the line most often missed. Without it the request succeeds and the header is still unreadable, so the card stays on that result. * is safe here: the probe sends no cookies or credentials, and the response carries nothing but the node name.
Two caveats:
- If you serve this manager over https, the browser blocks the plain-http probe, and the card cannot work whatever the CORS setup.
- Any answer that is not a
204with the cache header, such as a403, gives the same "cannot confirm" result.
Logs & Cache¶

Management → Logs & Cache - process logs, manage the disk cache, and detect corrupted or evicted files
Corruption scanning. Two scans, for two different problems:
| Scan | What it checks |
|---|---|
| Repeated-miss | Reads your logs for files that are on disk but keep missing. That usually means the cached copy is bad. |
| Structural | Opens the cache files and checks nginx headers, payload offsets, and recorded lengths. It flags only proven failures. |
The structural scan has two modes:
- Full Scan checks every eligible file and rebuilds the baseline.
- Incremental Scan checks only new, changed, or previously unresolved files.
To remove anything a scan finds, mount /cache without :ro.
That covers the daily surface. Management has more tabs behind it - expand below to see all of them.
See every Management page
Settings¶

Settings - authentication, demo mode, and display preferences.
Demo Mode fills the interface with simulated data, so you can try the UI out before you have any real cache history.
Integrations¶

Integrations - Steam, Epic, and Xbox sign-in, Battle.net and Riot (no account), and the Prometheus endpoint.
Data¶

Data - Data Import and Database Management.
Schedules¶

Schedules - every background service on its own interval, with Run Now on each mapping row. The Scheduled Prefill card at the bottom uses Run all.
Theme¶

Theme - switch between installed themes, import community themes, or upload your own.
Clients (nicknames and rules)¶

Clients - pick a client from the list to give it a nickname and set its rules (Count, Stats only or Hidden). The Prefill traffic and Hostname lookup rows open their own panes.
One nickname can cover several IP addresses - handy when a machine dual-boots or moves between wired and wireless and would otherwise show up as separate clients.
Prefill Sessions¶

Prefill Sessions - watch live and persistent prefill containers and review past runs.