Troubleshooting

Keep the version, steps and actual error, then use the matching symptom. Routine retries do not need data deletion, uninstallation or account recreation. Redact Cookies, playback keys, private URLs and personal details before sending screenshots.

Cannot open the app or 404

1. On fnOS, reopen through the HTTPS desktop icon. Check running status and /app/leelaa-strm in the address. Docker uses its actual mapped address without that prefix.
2. Record the exact failing page/action. Older versions had a homepage defect, but a wrong entry or proxy prefix can also cause 404; do not infer a version cause from the status alone.
3. Give the installer application/system versions, a redacted address and running status. Back up before updating; do not uninstall with data deletion.

Sign-in problems

Symptom	Handling
No initial administrator account delivered	Obtain the initialized application account from the installer; no web self-service collection exists
Session expired	Sign in again. Current new sessions last 30 days, but sign-out/password or account changes revoke earlier; previously issued older sessions do not extend automatically
Too many failures	Ten failures per username in five minutes: wait, then retry
Initial password change required	Complete it in 我的账号 and sign in again; see first sign-in
NAS option absent or no identity read	Docker has no option. On fnOS reopen through the desktop or use the application password
NAS identity changed/unbound/disabled/deleted	Read again or use an existing application password/contact the administrator. Repeated confirmation does not bypass account restrictions
NAS account has no password sign-in	Have the application administrator reset it in 用户管理 → 重置密码, then use the local username/new initial password and change it
Forgotten password	Members request an administrator reset. Preserve state and contact the maintainer for the sole administrator; do not overwrite newer state with an old backup

Software license unavailable

Check the actual deadline, network and system time under 应用授权. Query the original paid order; account connection, payment and local license installation are separate checks. An invalid license affects browsing, sync and both playback routes; dedicated player keys cannot bypass it. Follow software licensing and recovery, using the original purchasing account or matching file instead of repeating orders.

Credentials and directory browsing

Symptom	Handling
Saving rejected	The complete Cookie needs UID/SEID, no line breaks/control characters or duplicate fields
Saved but no listing	Local persistence is not validity. Check expiry, account and upstream limits, update and read again
Cannot connect to 115	Check NAS outbound access and upstream service; retry later
Incomplete directory response	The application refuses incomplete results to protect output. Keep the error and retry later; do not treat it as an empty complete directory
No way to obtain a Cookie	There is no QR/automatic acquisition option. Prepare legitimate credentials for your own account; do not request another person's account or publish credentials

Sync failure or timeout

Read the specific 运行记录 (Run records) message:

Note (examples)	Handling
More than 500 items	Split in 115 or create targets for small subfolders; 50-item browsing pages do not lift the limit
Cookie/service address missing	Finish credentials and service address first
3DVR duplicate names	Names must also be unique case-insensitively; organize source names
Foreign/modified output	Back up and have the maintainer review the manifest and manual files; do not delete the target tree or manifest
Another sync/delete running	Wait for a terminal state. After a browser timeout click 刷新记录 first; closing the page does not cancel the worker
Upstream refusal	Check actual error, Cookie and account state; retry later for upstream limits

Reading/new-file-generation failures preserve previous output; fix and 重新同步 (Resync) the original target. If an error says output switched, backup cleanup failed or a recovery marker exists, do not assume no files changed. Preserve state as below.

Playback failures

Symptom	Handling
401 during downstream scanning	Probing precedes playback. Configure dedicated authorization, update STRM, then scan
Ordinary relay returns 401	The player lacks this application's session; use dedicated authorization without administrator passwords/Cookies
Dedicated resource unavailable	Check software license, channel, target/issuing account and grant; an address change needs rotation
Playback request busy	Too many concurrent requests; retry later
Listed media will not open	Check downstream errors, codec compatibility and direct-link access; listing is not playback
Mid-stream stalls	Check Cookie, NAS-to-115 link exchange and player-to-CDN networking; do not assume the relay caused every stall
Old address after changes	Resync ordinary-address targets; rotate grants after a dedicated IP/port change, then rescan downstream

Preserve interrupted state

For these leftovers, stop related writers and preserve application data, output and records for the deployment maintainer. Do not simply delete them:

Item	Meaning and handling
.backup-…	Previous output retained during replacement; blocks later sync/deletion until reviewed against the current target
.sync-…	Staging output; the name alone does not establish it is disposable. Check active runs/recovery needs
.playback-pending-….json	Playback publication unfinished; review target files, grant state and backups together rather than removing the marker and retrying blindly

There is no complete automatic cleanup/one-click recovery interface. The maintainer must review the entire state instead of guessing which output is newest.

Problems after an upgrade

Preserve current data and old backups. Check the original data directory, private configuration and permissions. Have the maintainer follow backup and recovery, then verify users, targets, licensing and playback. Successful copying is not a successful recovery. Do not empty the user database, replace keys or regenerate installation identities.