ich777/docker-templates
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

ich777/Proxy-Server.xml aktualisiert

Browse Source
This commit is contained in:
Christoph Hummer
2025-04-02 12:03:55 +02:00
parent 4f13b588e2
commit 43e4b17da6
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
ich777/Proxy-Server.xml
View File

@@ -24,8 +24,8 @@ To connect the container to a already installed VPN container:
2. Enable the Advanced View on the top right corner from this Docker template and append:
`--net=container:CONTAINERNAME` 
To the Extra Parameters (you have to change `CONTAINERNAME` to the VPN Docker container name eg: `--net=container:binhex-delugevpn` when the VPN Docker container name is `binhex-delugevpn` - case sensitive!).
3. Go to the VPN Docker template and create two new port mappings with the button `Add another Path, Port, Variable, Label or Device`, by default 8118 (for http/https proxy) and 1030 (for SOCKS5 proxy) both TCP protocol and with host/container port set to the same port.
4. When you've done that you can connect the application(s) to the proxy to the host IP from the VPN Docker container, by default with 8118 (for http/https proxy) and 1030 (for SOCKS5 proxy)
3. Go to the VPN Docker template and create two new port mappings with the button `Add another Path, Port, Variable, Label or Device`, by default 8118 (for http/https proxy) and 1080 (for SOCKS5 proxy) both TCP protocol and with host/container port set to the same port.
4. When you've done that you can connect the application(s) to the proxy to the host IP from the VPN Docker container, by default with 8118 (for http/https proxy) and 1080 (for SOCKS5 proxy)

**Note for Firefox and Chrome:** Firefox and Chrome natively don't support authentication for a SOCKS5 proxy, it is recommended to use a extension like FoxyProxy supports authentication).