Github/docker-qBittorrentvpn
1
0
Fork 0
mirror of https://github.com/MarkusMcNugen/docker-qBittorrentvpn synced 2024-11-23 02:54:57 +00:00
Code Issues Projects Releases Wiki Activity

Minor update to readme issues section

Browse Source
This commit is contained in:
Amish Bhadeshia 2015-05-29 14:04:18 +01:00
parent f54b7c1f40
commit 296c9adfea
1 changed files with 7 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -79,6 +79,13 @@ $ docker run --privileged -d \
As described in the "Run container from Docker registry" section, this will start a container with default settings. This means that you should have the folders "completed, incomplete and watch" in /your/storage/path, and pia-credentials.txt in /your/config/path. As described in the "Run container from Docker registry" section, this will start a container with default settings. This means that you should have the folders "completed, incomplete and watch" in /your/storage/path, and pia-credentials.txt in /your/config/path.
### Issues
If you are having some issues running the local build then please ensure you are using the latest version of docker. To do this use the following table. Using the latest table verison will resolve 95% of issues.
| Distribution | Command |
|--------------|---------|
| Debian | ```sudo apt-get update && sudo apt-get install docker.io``` |
## Access the WebUI ## Access the WebUI
But what's going on? My http://my-host:9091 isn't responding? But what's going on? My http://my-host:9091 isn't responding?
This is because the VPN is active, and since docker is running in a different ip range than your client the response to your request will be treated as "non-local" traffic and therefore be routed out through the VPN interface. This is because the VPN is active, and since docker is running in a different ip range than your client the response to your request will be treated as "non-local" traffic and therefore be routed out through the VPN interface.