Set up your connection
Helm needs a running qBittorrent server with its Web UI enabled.
- In qBittorrent settings, enable the Web User Interface. Note its listening port and configure a username and password.
- Find the server’s local network address. Use the server’s LAN address, not
localhost, which refers to your iPhone or iPad. - In Helm, enter the server’s address and port and your Web UI credentials. Use
https://if the Web UI has HTTPS turned on, for examplehttps://nas.example.com:8080. Plainhttp://, for examplehttp://192.168.1.20:8080, works only for addresses on your local network. Your actual address and port may differ. - Allow local network access when iOS asks, then connect.
Using HTTPS
- A server on a public address or name needs a certificate your iPhone or iPad already trusts, such as one from Let’s Encrypt.
- A self-signed certificate works only for local addresses. The first time you connect, Helm shows the certificate’s fingerprint. Check that it matches your server, then trust it. If the certificate later changes, Helm asks again before sending your password.
Having trouble?
- Confirm both devices can reach the same trusted network and that the server is running.
- Check the address, port and credentials, and ensure the server firewall permits connections from your local network.
- If local network access was denied, enable it for Helm in iOS Settings and try again.
- If using a reverse proxy, include its path in the server address.
- If Helm says a public server’s certificate is not trusted, replace it with one from a public certificate authority. Self-signed certificates work only for local addresses.
- If the correct password is rejected and you connect through a reverse proxy, a NAS port forward or a remapped Docker port, use qBittorrent’s own Web UI port, or turn off Host header validation in qBittorrent’s Web UI settings. With that check on, qBittorrent rejects requests addressed to any other port.
Plain HTTP does not encrypt credentials or traffic, so Helm allows it only on your local network. Do not expose the Web UI to the public internet without HTTPS, and do not weaken its authentication to make a connection work.
Contact support if you still need help. Never send passwords, cookies, or private torrent links.