English
FAQ
The app opens to a 404
Reopen through the normal entry and check running status: fnOS keeps the application prefix, Docker does not. An old homepage defect is one possible cause, but 404 alone does not identify it. Keep the version, real error and redacted address; see troubleshooting. Do not uninstall with data deletion.
Where are the initial administrator credentials?
The administrator account is system-initialized and delivered by the installer; there is no web self-service collection. Change the initial password at sign-in, after which it stops working. If no account was delivered or sign-in fails, see Troubleshooting.
I forgot my password
- Member: ask an application administrator to reset your password in user management; you then sign in with the new password and complete the first password change.
- Administrator: the initial password stopped working after the first change and cannot be recovered by yourself. Preserve complete data and have the maintainer review backups against current state. Do not directly overwrite newer data with an older backup or uninstall with data deletion.
Does sync support recursion or schedules?
No. A sync processes only the current level of the chosen directory and is always triggered manually; one directory holds at most 500 items (files plus folders). Create separate targets for subdirectories. Browsing paginates 50 items per page, which never lifts the sync limit.
The page reports an expired session or missing administrator rights
Reopen the app and sign in again with the app's local account. Regular members manage their own account and view shared license status under 应用授权; configuration, directory browsing and target management require the application administrator created by system initialization. A fnOS (NAS) administrator flag never grants application administration.
Browsing still fails after saving the Cookie
"Credentials saved" only means local storage succeeded. Check whether the Cookie is complete, whether it expired, and whether 115 limits access. After updating credentials, read again in Cloud directory(云端目录).
Why must the service address keep the app path
The fnOS gateway uses an app-specific prefix. Missing /app/leelaa-strm may hit the NAS's own routes and produce a 404. The address must also be reachable from the actual playback device.
Old files still use the old address after changing the service address
Saving settings never rewrites existing STRM files. Re-sync the affected targets, then have downstream apps refresh their media libraries.
The sync timed out — can I click again?
Refresh targets and run records first. A timeout means the browser has not confirmed the result; the server may still be processing. Decide on a retry only after confirming the outcome, to avoid duplicate operations.
I browsed into a subdirectory — why doesn't the target have all files?
A sync processes only the current level of the chosen directory, never subdirectories recursively. Create one target per work directory and check the range limits reported by the service.
Does deleting a target delete the cloud videos?
No. Deletion covers the target and the generated files managed by this service; the UI asks for confirmation. Original cloud files remain untouched.
A software license expired; should I purchase again?
Refresh an existing purchase and query the original order first. Account purchases, .llab and historical .lltf use different recovery options; none restores application accounts, Cookies or targets. See software licensing and recovery. Ordinary members should contact the application administrator.
STRM files exist but the player returns 401, 403 or cannot open
Normal relay addresses require signing in to this app, which standalone players normally lack. Use the dedicated playback authorization channel for standalone players. Never bypass by disabling authentication or exposing the Cookie.
The playback authorization key was lost
The key is shown once at creation. Create a new authorization for the target (this rewrites its STRM and revokes the old grant), then rescan the media library.
Can I copy STRM files to a computer or phone and play them directly?
A STRM file is not a video; it is a relay address pointing to the streaming service on your NAS:
- Normal relay addresses (the default generated STRM) cannot play without signing in to this app.
- Dedicated playback-authorization addresses need no sign-in: any device that can read the STRM and reach the NAS on the internal network can play the matching resources — so never share or publish dedicated STRM files.
The intended usage is to let a player or media app scan the generated directories — see Connect media apps and playback authorization.
How is NAS sign-in different from password sign-in?
Both enter the same app account system. NAS sign-in is only available on fnOS deployments and requires confirming the displayed name on the page; the first confirmation creates an independent account (regular member). Password sign-in works anywhere. Neither signs in automatically, and neither changes roles — see the account chapter.
What can a regular member do?
Members manage their own account and view shared 应用授权 status. NAS-only members need an administrator-set initial password before password changes or unbinding. Cloud credentials, directory browsing, target management and user management require the application administrator. Administrators are created by system initialization only; daily actions can never create or promote one.
Data will not open after an upgrade
Stop the app and keep the scene; never delete files inside the app data directory or uninstall and reinstall. Verify the full backup set per Install or contact support.