mirror of
https://github.com/haugene/docker-transmission-openvpn.git
synced 2025-08-12 09:17:07 +02:00
d042c7da52
* Update vpn-networking.md yea, used your guide today and was a bit irritated that if you run the command for the proxy container it gets a random name. * Update vpn-networking.md forgot the backslash
33 lines
1.8 KiB
Markdown
Executable File
33 lines
1.8 KiB
Markdown
Executable File
## COMING SOON
|
|
|
|
**NOTE:** This page is just moved from it's previous location. A re-write is coming and I know that
|
|
there are links to this page that promises more than what's here now. I'm [on it (#1558)](https://github.com/haugene/docker-transmission-openvpn/issues/1558)
|
|
|
|
|
|
## Access the WebUI
|
|
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.
|
|
|
|
### How to fix this
|
|
The container supports the `LOCAL_NETWORK` environment variable. For instance if your local network uses the IP range 192.168.0.0/24 you would pass `-e LOCAL_NETWORK=192.168.0.0/24`.
|
|
|
|
Alternatively you can reverse proxy the traffic through another container, as that container would be in the docker range. There is a reverse proxy being built with the container. You can run it using the command below or have a look in the repository proxy folder for inspiration for your own custom proxy.
|
|
|
|
```
|
|
$ docker run -d \
|
|
--link <transmission-container>:transmission \
|
|
-p 8080:8080 \
|
|
--name transmission-openvpn-proxy \
|
|
haugene/transmission-openvpn-proxy
|
|
```
|
|
## Access the RPC
|
|
|
|
You need to add a / to the end of the URL to be able to connect. Example: http://my-host:9091/transmission/rpc/
|
|
|
|
## Controlling Transmission remotely
|
|
The container exposes /config as a volume. This is the directory where the supplied transmission and OpenVPN credentials will be stored.
|
|
If you have transmission authentication enabled and want scripts in another container to access and
|
|
control the transmission-daemon, this can be a handy way to access the credentials.
|
|
For example, another container may pause or restrict transmission speeds while the server is streaming video.
|