Motrix v2.0.0-beta.28 release notes

Motrix 2.0.0-beta.28

Motrix 2.0.0-beta.28 resolves beta blockers in direct-download naming and finalization, RPC lifecycle, proxy handling, Windows networking and integration, and Snap publication. It is intended for public distribution only after every protected release gate passes.

Highlights

HTTP(S) downloads now derive safe final filenames after redirects, request rewriting, plugin hooks, and proxy-aware remote metadata probes. Explicit user filenames remain authoritative, while failed probes retain a safe URL-based fallback (#1976).
The Files inspector keeps the logical HTTP/FTP destination name instead of exposing aria2's temporary .motrix suffix. Finalization rebases persisted file records after a successful rename without changing BitTorrent, Magnet, or multiplexed-download paths (#2001).
An explicitly empty RPC password now enables intentional no-token mode. Motrix still binds aria2 RPC to loopback, disables permissive cross-origin access, refreshes the RPC client before the first call to a restarted engine, and coalesces concurrent restart requests (#1987, #1988).
Native BitTorrent traffic has the same boundary regardless of the selected proxy: peer connections, DHT, and UDP trackers remain direct. Only HTTP(S) requests associated with a torrent, such as HTTP(S) trackers and Web Seeds, can use the download proxy. This release adds an authenticated loopback HTTP bridge so SOCKS5 also works for regular HTTP(S) downloads, tracker-list refreshes, and that BitTorrent HTTP(S) traffic. Per-listener authentication is generated in memory and removed when the bridge stops (#1977).
Motrix now uses @motrix/nat@0.1.1, improving Windows default-route selection and NAT mapping in multi-adapter environments such as Tailscale (#1999).
Windows CLI discovery now starts native executables directly and reserves cmd.exe for batch shims, fixing Node.js paths under Program Files (#1998).
The Windows installer restores the dedicated .torrent association icon while preserving the installer-owned Default Apps design (#2003).
The Downloads page restores its empty state when only removed records remain. Protected beta tags also use the Store's scoped edge channel correctly when publishing the verified two-architecture Snap set to latest/edge (#1997, #1996, #2002).

Before testing

This is prerelease software. Back up existing Motrix application data and downloads before installing it. Migration from Motrix v1 data has not yet been validated, so do not use your only copy of v1 data with this beta.

When practical, test v2 in parallel using a separate OS account, machine, or Docker data directory. Pay particular attention to redirected HTTP downloads, downloads using each proxy protocol, the documented BitTorrent proxy boundary, RPC no-token mode, engine restarts, and Windows networking or file associations relevant to your environment.

After the protected release completes, Snap testers can install the strictly confined build with sudo snap install motrix --edge. Existing installations tracking latest/edge should upgrade to the same beta.28 revision set.

Planned downloads after release gates pass

Distribution	Architectures	Planned output
macOS 12 or later	`arm64` (Apple Silicon), `x64` (Intel)	DMG and ZIP
Windows	`x64`	Unsigned NSIS installer (`.exe`) and ZIP
Linux	`x64`, `arm64`	AppImage, DEB, and RPM
Flatpak Native Host companion	`linux/x64`, `linux/arm64`	`Motrix-Native-Host-2.0.0-beta.28-linux-<arch>.tar.gz`
Docker Hub / GHCR	`linux/amd64`, `linux/arm64`	Immutable `2.0.0-beta.28` tag in both registries
Snap Store	`amd64`, `arm64`	Verified build set on `latest/edge`

After every container gate passes, the versioned image references will be docker.io/motrixapp/motrix-server:2.0.0-beta.28 and ghcr.io/agalwood/motrix-server:2.0.0-beta.28. See the Docker Server deployment guide for storage, networking, and upgrade guidance.

Distribution notes

AppImage desktop integration is opt-in and confined to the current user's XDG data directory. Browser-extension hand-off is not yet available from the AppImage package because its Native Messaging host does not have a stable path outside the mounted image.
Flatpak is validated separately and is not published by the release tag; the GitHub prerelease includes its Native Host companion archives.
Windows arm64 and all 32-bit packages are not available.
Windows packages are unsigned and may trigger a Windows SmartScreen warning. Download them only from the official GitHub prerelease after it is published.
Beta container tags are immutable and do not update latest, stable, or other stable floating tags.
The Snap package is strictly confined. Its approved personal-files interface is limited to registering Native Messaging host manifests for supported browsers. Beta publication updates latest/edge only; it does not promote the build to candidate or stable.

Feedback

Please report reproducible problems through GitHub Issues. Include your operating system, architecture, package type, and the steps needed to reproduce the issue.

What's Changed

fix(snap): honor scoped edge channel credentials by @agalwood in https://github.com/agalwood/Motrix/pull/1996
fix(cli): spawn windows executables directly by @agalwood in https://github.com/agalwood/Motrix/pull/2000
fix: resolve beta blockers in downloads, RPC, NAT, and proxy by @agalwood in https://github.com/agalwood/Motrix/pull/2002
chore(release): prepare 2.0.0-beta.28 by @agalwood in https://github.com/agalwood/Motrix/pull/2004

Full Changelog: https://github.com/agalwood/Motrix/compare/v2.0.0-beta.27...v2.0.0-beta.28

Motrix v2.0.0-beta.28