English
Installation and upgrades
For fnOS, choose the matching FPK: x86_64 for Intel/AMD or aarch64 for ARM64. Docker only has local-candidate instructions, without a formal image distribution or ordinary-user first-account delivery entry.
Package downloads
| Architecture | Package | Checksum |
|---|---|---|
| Intel / AMD · x86_64 | FPK · 5.5 MiB | SHA-256 |
| ARM64 · aarch64 | FPK · 5.7 MiB | SHA-256 |
Before installing, verify the FPK's SHA-256 using its matching .sha256 file.
Install
- Open fnOS App Center → Manual installation and select a verified FPK. Some system versions start immediately after file selection, so check the product, version and architecture first.
- Open 网盘流 from the HTTPS fnOS desktop. Older install/uninstall wizards may use the previous name; check actual application information and version.
- Use the system-initialized application administrator account delivered by the installer. If none was delivered, contact the installation maintainer. There is no web initial-administrator collection page. Do not send passwords in chat or screenshots.
- Complete the initial password change in 我的账号, then sign in again.
- Open 应用授权 and check the real trial/purchased state. With a valid license, follow first sync and playback to connect 115, save the address and verify a small target.
Completion check: the new password works, administrator features appear, and a real 115 directory loads under a valid license. Opening a page, confirming NAS identity or saving credentials alone is insufficient.
NAS identity and application permissions
The fnOS entry can offer 使用 NAS 登录 → 确认登录. A new trusted identity becomes an independent ordinary member. NAS administrator status does not grant application administrator permissions. Existing bindings reuse the application account. To retain an existing local identity, sign in with its password and bind NAS explicitly.
Only initialization creates the first administrator. Daily creation makes ordinary members. Members manage their own account and view the shared license; they cannot read cloud settings, browse folders or manage targets. See my account.
Before upgrading
- Wait for sync/deletion and payment-result checks, and record the version.
- Stop the application. Back up complete state, generated output and existing private deployment configuration as described in backup and recovery. Do not copy just one database file.
- Install a trusted matching update in App Center while retaining data.
- Sign in again and check original targets, records, service address, licensing and 115 browsing. Resync a small target, then scan and play downstream.
For startup failure, lost administrator access or repeated errors, preserve state and contact the maintainer. Do not clear accounts/data or uninstall to bypass the problem.
Backup and recovery
Complete application state, generated STRM and original cloud media are different data. License recovery files contain no accounts, Cookie, targets or run records.
There is no user-facing whole-library export/restore page. A deployment maintainer must stop writers, preserve current state, then check and recover complete backups and permissions. Afterwards check targets, service address, credentials, playback grants and files. Another device also requires official software-license recovery; file copying alone does not grant access. See data and privacy.
The page returns 404
Reopen through the HTTPS fnOS desktop and check the address/running state. Docker does not use the fnOS prefix. Older versions had a homepage-routing defect, but 404 alone does not identify its cause. Keep the version and real error and follow troubleshooting.
Uninstall
The current fnOS wizard only keeps data: accounts, license state, credentials, targets, records and output remain. It does not delete 115 originals. Uninstallation is not a complete backup and does not restart the trial. Before any later data removal, keep complete backups and the original purchasing account/license materials. Have the NAS maintainer check directories and downstream dependencies rather than deleting a shared folder blindly.