dockage/tor-privoxy

Docker Tor proxy (http and shell) built on Alpine Linux

tor-privoxy's Issues

Control Port mismatch

Just a question on how the file is built. The docs say:

The exposed ports are:
9050: Tor proxy (SOCKS5)
9051: Tor control port
8118: Privoxy (HTTP Proxy)

But the dockerfile changes the control port in the tor config file from 9051 to 9052. Is there some other listening thing going on behind the scenes that I am not seeing where control is passed from 9051 to 9052? Or should the torrc file have 9051 as control?

&& sed -i \
        -e 's/#SOCKSPort 192.168.0.1:9100/SOCKSPort 0.0.0.0:9050/g' \
        -e 's/#ControlPort 9051/ControlPort 9052/g' \
        -e 's/#%include \/etc\/torrc\.d\/\*\.conf/%include \/etc\/torrc\.d\/\*\.conf/g' \
        /etc/tor/torrc \

Support website is down?

The support website for this project is supposedly located at https://dockage.dev/ (according to the README), however the domain doesn't exist? Nslookup tells me the domain isn't registered.

ControlPort on 9052, but exposed port on 9051

Your torrc file configuration changed the ControlPort from 9051 to 9052, however, you are exposing 9051. Can you explain if that is a deliberate choice or a mistake?

Cycle rebooting

If i create container by script which written on js using dockerode, container is rebooting after 20-60 seconds

But if i create via docker run --name='tor-privoxy' -d \ -p 9050:9050 \ -p 9051:9051 \ -p 8118:8118 \ dockage/tor-privoxy:latest, it's working normally
What can be problem?

Dockerfile base image outdated, January 2023?

Hello,
I noticed that the image of this repository doesn't support the arm64 architecture (raspberry pi). I therefore tried to switch components in the dockerfile to support the arm64 architecture. I noticed that the tor-privoxy image is based on a custom alpine image from dockage too. That image has a tag that seems to point to a outdated version.

The tor-privoxy dockerfile says:
FROM dockage/alpine:3.9-openrc

At the dockage/alpine repository (see: https://github.com/dockage/alpine 2023.01.31) there isn't the mentioned tag in the "supported" list. But there is a tag :3-openrc that seems to pick the latest costum dockage alpine3 image (currently 3.16.2 2023.01.31) that supports openrc.
That image also supports the arm64 architecture and builds correctly on my Raspberry Pi. I tested the tor-proxy with some https requests and the control port with an ip-change. Both work correctly. I wasn't able yet to test other functions or architectures too.

But for now I come to the conclusion that the above mentioned Dockerfile of this tor-privoxy repository line should be changed to:
FROM dockage/alpine:3-openrc

Is this correct? If it isn't, why is the tor-privoxy image based on a "old" custom image?

Yours Sincerely

obfs4 support

Any plans to add obfs4 support?

How to turn on 0.0.0.0:9050

I want to run a python script with this image, but It does not connect I think i need to turn 0.0.0.0:9050 in torrc. How Can I do that?

Missing Health Check

Is there a way to add a health check to this image/container? I have done some in the past using curl but I do not want to create a custom image just to add curl in. Is there something in there already that can validate through a check to check.torproject.org? I played around with NC doing this: nc -z -v 127.0.0.1 9050 ...but not sure if that is the best way.

Sorry

Sorry

how to set local proxy

In order for all Torus traffic to go through a proxy
Socks5Proxy 127.0.0.1:23000?

This version of Tor (0.4.7.10) is obsolete

I got this warning:

Please upgrade! This version of Tor (0.4.7.10) is obsolete, according to the directory authorities. Recommended versions are: 0.4.8.1-alpha,0.4.8.2-alpha,0.4.8.3-rc,0.4.8.4,0.4.8.5,0.4.8.6,0.4.8.7,0.4.8.8,0.4.8.9,0.4.8.10,0.4.8.11