The web UI is accessible outside of my local network. Can I block this?
Posted: Sat May 20, 2017 12:03 pm
I've set up the web UI to serve on port 8090, and this works fine. I can type http://raspberrypi:8090 in my local network to successfully see the web UI.
However I've noticed (from the standard output when running qbittorrent-nox) that it is also available via http://[external_ip_address]:8090, which I'm not really after.
Is there anyway to disable this external access? I know that transmission-daemon has an ip whitelist, is this available with qbittorrent, or otherwise?
If the external access cannot be disabled, should I be conscious of network security implications? I do have a password set for the web UI, but I was considering if just generally having that port open externally creates any security implications in of itself. I'm not an expert on networking so I'm unsure.
However I've noticed (from the standard output when running qbittorrent-nox) that it is also available via http://[external_ip_address]:8090, which I'm not really after.
Is there anyway to disable this external access? I know that transmission-daemon has an ip whitelist, is this available with qbittorrent, or otherwise?
If the external access cannot be disabled, should I be conscious of network security implications? I do have a password set for the web UI, but I was considering if just generally having that port open externally creates any security implications in of itself. I'm not an expert on networking so I'm unsure.