While not a massive issue, I find myself needing to re-add my server/ip every time I restart the device running the qBittorrent host (my IPV4 address changes upon reboot). This requires direct access on my host device and running ipconfig to find out my new address.
This could be bypassed, though, if API implementation were added; the qRemote app would essentially be paired to the qBittorrent host client and would no longer necessitate adding a new server every time I reboot. It also would bypass the need to set a username and password (this is a requirement only of the app, it’s not technically needed AFAIK if on the same local network); qBittorrent has settings to allow connections on local network to bypass the authentication step.
Finally, this configuration would be set until the API key is regenerated in the desktop app. Even through restarting the client or the entire host machine, the API key stays the same (AFAIK) so it would always be able to access the server.
While I acknowledge I may be wrong about how the API works, or if it’s changed upon client restart, it would still be helpful simply to bypass the authentication username and password process!
**Priority (check one)
[ ] 🆘 P1: “ Not having this is a deal breaker
[ ] 🚨P2: Other qbittorrent remote apps have similar functionality
[ X ] ⚠️P3: “Would be really cool to have”
[ ] 👨💻P4: “Whenever you get around to it”
[ ]💡 P5: “Heres a random idea”
While not a massive issue, I find myself needing to re-add my server/ip every time I restart the device running the qBittorrent host (my IPV4 address changes upon reboot). This requires direct access on my host device and running ipconfig to find out my new address.
This could be bypassed, though, if API implementation were added; the qRemote app would essentially be paired to the qBittorrent host client and would no longer necessitate adding a new server every time I reboot. It also would bypass the need to set a username and password (this is a requirement only of the app, it’s not technically needed AFAIK if on the same local network); qBittorrent has settings to allow connections on local network to bypass the authentication step.
Finally, this configuration would be set until the API key is regenerated in the desktop app. Even through restarting the client or the entire host machine, the API key stays the same (AFAIK) so it would always be able to access the server.
While I acknowledge I may be wrong about how the API works, or if it’s changed upon client restart, it would still be helpful simply to bypass the authentication username and password process!
**Priority (check one)⚠️ P3: “Would be really cool to have”
[ ] 🆘 P1: “ Not having this is a deal breaker
[ ] 🚨P2: Other qbittorrent remote apps have similar functionality
[ X ]
[ ] 👨💻P4: “Whenever you get around to it”
[ ]💡 P5: “Heres a random idea”