fnOS (Native FPK)

The native fnOS package runs Motrix on your NAS without Docker. Open it from the fnOS desktop and manage HTTP, FTP, BitTorrent and magnet downloads in your browser. The package includes the download engine and its runtime; you do not need to install Node.js or aria2 on the NAS.

This is an administrator-shared instance. Sign in with a fnOS administrator account. All administrators manage the same tasks and application settings; ordinary users cannot access it. Tasks are not isolated by administrator.

Choose your download

Open Downloads → NAS. Download the FPK and its SHA-256 file from the same release, choosing the architecture of your NAS, not the computer running your browser.

NAS processorPackageChecksum file
Intel / AMD, x64 (x86_64)Motrix-VERSION-fnos-x64.fpkMotrix-VERSION-fnos-x64.fpk.sha256
ARM64 (aarch64)Motrix-VERSION-fnos-arm64.fpkMotrix-VERSION-fnos-arm64.fpk.sha256

VERSION means the version in the downloaded filename, without the leading v. These are direct downloads from official GitHub Releases. Motrix is not listed in the fnOS App Center catalog; use Manual Install.

The package declares fnOS 1.2.0401 or later. Native x64 and ARM64 builds pass automated package and lifecycle checks. Device acceptance has covered fnOS 1.2.0903 on ARM64; x64 hardware, the minimum declared fnOS version, and mobile/FN Connect still need device coverage.

Check the downloaded file

Keep the FPK and its .sha256 file in the same folder. On Linux, replace VERSION with the downloaded version and run:

sha256sum -c Motrix-VERSION-fnos-x64.fpk.sha256

On macOS, use shasum -a 256 -c instead of sha256sum -c. On Windows PowerShell, run:

Get-FileHash .\Motrix-VERSION-fnos-x64.fpk -Algorithm SHA256

Compare the result with the hash in the .sha256 file. For ARM64, replace x64 with arm64. If the hashes differ, download both files again before installing.

Install and open Motrix

  1. Sign in to fnOS with an administrator account.
  2. Open App Center → Manual Install, select the downloaded .fpk, and follow the wizard.
  3. Keep the default Client connection port 16802 unless it conflicts with another service. This port is for CLI and optional browser-extension clients.
  4. Start Motrix and open it from the fnOS desktop. Its Web interface uses the fnOS gateway; you do not need the Docker edition’s port 8080.
  5. Review the application notice, choose or authorize a download folder, then add a download.

Note

FPK installation does not migrate a separate desktop or Docker instance. Keep that instance and its data backed up; do not point both applications at the same active task database.

Download folders and permissions

The package declares a motrix/downloads share. To use another shared folder, select it with the fnOS directory picker and grant the application access. Motrix also checks the current administrator’s file permissions.

  • Pasting a path does not grant access to it.
  • Opening a .torrent through a fnOS file association requires the torrent file to be in an authorized, readable folder. You can also upload a torrent through the browser.
  • If a disk or shared folder is unavailable, restore access before resuming tasks. Motrix does not recreate an unavailable share on an unmounted volume.
  • Stop Motrix before revoking a download-folder grant. Revocation blocks later path checks but does not immediately stop an engine file that is already open.

See Adding tasks and Managing tasks for everyday downloads.

Browser extension

Install Motrix Extension on the computer where you browse. Connecting it to the NAS is optional and is off by default.

  1. In fnOS Application settings for Motrix, enable Browser Extension connections.
  2. Set Extension connection URL to an address reachable from the extension, for example ws://nas.local:16802. Use wss:// when configured through a TLS reverse proxy.
  3. Set Motrix Web URL to the full address you actually use in the browser, including /app/motrix/, for example https://nas.example/app/motrix/. If you use HTTP on a trusted network, explicitly allow HTTP pairing pages in the same settings. Setting an HTTPS URL does not authorize an HTTP page.
  4. Restart Motrix after saving these settings.
  5. Add a remote Server connection in the extension using the configured WS/WSS address and start pairing.
  6. Open Motrix as a fnOS administrator, claim the pairing request, and enter the displayed code in the extension. The client is bound to the administrator who claimed it.

Disabling or demoting that account, or revoking its client authorization, removes the client’s access. Other administrators cannot simply retrieve a claimed request’s code. If an optional extension setting is invalid, the normal fnOS Web interface and CLI remain available.

Command-line client

Install the Motrix CLI on the computer that will send commands. Use the NAS client’s configured port, 16802 by default, and approve its pairing request in the fnOS administrator Web interface. The credential uses that administrator’s permissions; a fnOS browser cookie is not a CLI credential.

The native package’s client port is separate from the Docker guide’s default 16801. Changing the port in fnOS Application settings requires restarting Motrix.

Upgrade and back up

  1. Pause downloads and stop Motrix before taking a consistent backup of its application data and download folders.
  2. Download the newer FPK for the same NAS architecture and verify its checksum.
  3. Use fnOS Manual Install to upgrade the existing application in place. Keep application data when fnOS presents a retention choice.
  4. Open Motrix and check tasks, directory grants and connected clients before resuming downloads.

fnOS requires the new package version to be greater than the installed version. Do not uninstall just to bypass a same-version error: uninstalling can clear directory grants even when task data is retained. Reselect authorized folders if they were cleared. Retain the engine’s pre-upgrade database backups; older engines cannot open newer database formats.

Troubleshooting

SymptomWhat to check
Package cannot be installedConfirm the NAS architecture, fnOS version, checksum, and that this is a newer package version.
Access denied when opening MotrixUse an enabled fnOS administrator account. Ordinary users are not supported.
A download folder is rejectedReauthorize it with the fnOS picker, check your account’s permissions, and confirm the volume is mounted.
Browser extension cannot pairCheck the client port, reachable WS/WSS URL, exact Web URL, HTTP consent, and whether Motrix was restarted. Claim the request with the intended administrator.
CLI cannot connectUse the native client’s configured port, not the Web gateway or Docker port, and check for a port conflict.
No native package for your NAS OSUse the Docker deployment guide if the NAS supports Docker. FPKs install only on fnOS.