Proxy and DNS

Motrix can route its network traffic through a proxy — useful behind corporate networks, for privacy, or when a mirror is only reachable through a tunnel. Configuration lives in Settings → Network.

Configuring the proxy

Turn on Enable proxy and fill in the server:

FieldNotes
Protocolhttp, https, or socks5
Host / PortThe proxy server’s address
AuthenticationEnable and supply User / Password if the proxy requires a login

If your operating system already has a proxy configured, Import from system copies its host and port in one click.

Choosing what gets proxied

The Apply to section controls which traffic uses the proxy, with three independent scopes:

ScopeCovers
DownloadsFiles fetched by the download engine (applied as aria2’s all-proxy)
App update checkThe auto-updater’s HTTPS requests
Tracker syncThe periodic curated-tracker-list refresh

This separation matters in practice: you might want downloads to go through a tunnel while update checks stay direct — or the reverse, if your network blocks GitHub but not your download sources.

Note

The Downloads scope proxies HTTP, HTTPS, and FTP transfers. BitTorrent peer-to-peer connections are not routed through the proxy — the underlying engine does not support proxying BT peer traffic.

Bypass list

Hosts in the Bypass list connect directly, skipping the proxy. One host per line; wildcards such as *.local are allowed. The bypass list applies to the Downloads and App update scopes.

192.168.1.10
*.local
nas.home.arpa

Per-task proxy

A proxy can also be set for a single task in the New Task dialog’s Advanced panel — see Adding tasks. A per-task proxy overrides the global one for that task.

DNS resolution

The DNS section chooses how the download engine resolves hostnames — the DNS lookup setting has three modes:

ModeBehavior
Auto (default)Start with the engine’s built-in asynchronous resolver; if it hits a recognized transport failure, fall back to the system resolver for the rest of the session and notify you
System DNSAlways use the operating system’s resolver
Built-in DNSAlways use the engine’s asynchronous resolver

Auto is the right choice for almost everyone. Switch to System DNS if your network relies on a local resolver (VPN split-DNS, corporate DNS, Pi-hole style filtering) and downloads resolve to the wrong addresses.

Tip

If you see the notification “retried with system DNS”, that’s Auto mode doing its job — the built-in resolver couldn’t reach a DNS server, and Motrix switched over without failing your downloads.