Closed B0G0311 closed 1 year ago
Since your test curl
command is returning a VPN IP as expected, your issue probably lies outside the scope of proton-privoxy.
AFAIK Privoxy only supports HTTP traffic, so it might not be feasible to use it for BitTorrent.
I setup proton-privoxy in a docker-compose stack to mainly work alongside my qbittorrent and prowlarr containers yet, it does not seem to be allowing connections. My output for '$ curl --proxy http://127.0.0.1:8888 https://ipinfo.io/ip' shows an ip address and appears to be working. The problem presents itself when I connect to proxy to qbittorrent through the proxy server setting in the interface but instead it shows the firewalled connection status and no upload or download goes through the container.
My docker-compose.yml `version: "3"
services: proton-privoxy: image: walt3rl/proton-privoxy container_name: proton-privoxy environment:
proton-connect
prowlarr: image: lscr.io/linuxserver/prowlarr:latest container_name: prowlarr environment:
${TRAEFIK_PROWLARR}
)"Watchtower Update
"com.centurylinklabs.watchtower.enable=true"
Ip filtering
- "traefik.http.routers.prowlarr.middlewares=whitelist@file"
restart: unless-stopped
qbittorrent: image: lscr.io/linuxserver/qbittorrent:latest container_name: qbittorrent environment:
${TRAEFIK_QBIT}
)"Watchtower Update
"com.centurylinklabs.watchtower.enable=true"
Ip filtering
- "traefik.http.routers.qbittorrent.middlewares=whitelist@file"
restart: unless-stopped
networks: proxy: external: true name: proxy
proton-connect:`
My proton-privoxy container logs:
$ docker logs proton-privoxy Connecting to US-VA#38 via UDP... Connected! 2023-05-16 14:05:42.707 7fec29c62b48 Info: Privoxy version 3.0.33 2023-05-16 14:05:42.707 7fec29c62b48 Info: Program name: privoxy 2023-05-16 14:05:42.707 7fec29c62b48 Info: Listening on port 8080 on IP address 0.0.0.0
I even tried port forwarding the privoxy container in my router with the ip of the host pc and the containers port.