@gus Sorry, but the script does not work for me (Debian 12, fresh install with IPV6) Most likely it is just the Docker container. The Docker never gets into the state of a bridge correctly. It is behind a “Docker-NAT”, which is good, but the ORPort is forwarded (and even in a wrong way to work).
After this fix Your server has not managed to confirm reachability for its ORPort - #6 by atari it works without problems.
docker-compose.yml has to look like this imho:
services:
webtunnel-bridge:
restart: always
environment:
- NICKNAME=$BRIDGE_NICKNAME
- PT_PORT=15000
- OR_PORT=127.0.0.1:auto
- EMAIL=$OPERATOR_EMAIL
- WEBTUNNEL_URL=$URL
- WEBTUNNEL_ENABLE_ADDITIONAL_VARIABLES=1
- WEBTUNNELV_AssumeReachable=$WEBTUNNELV_AssumeReachable
volumes:
- 'webtunnel-tor-state:/var/lib/tor'
user: debian-tor
ports:
- '127.0.0.1:15000:15000'
container_name: webtunnelBridge
image: 'thetorproject/webtunnel-bridge:latest'
labels:
- "com.centurylinklabs.watchtower.enable=true"
watchtower:
restart: always
image: containrrr/watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
- /etc/timezone:/etc/timezone:ro
environment:
- WATCHTOWER_CLEANUP=true
- WATCHTOWER_LABEL_ENABLE=true
- WATCHTOWER_INCLUDE_RESTARTING=true
labels:
- "com.centurylinklabs.watchtower.enable=true"
volumes:
webtunnel-tor-state:
and .env should be setup like this:
$ truncate --size 0 .env
$ echo "URL=https://yourdomain/and/path" >> .env
$ echo "OPERATOR_EMAIL=your@email.org" >> .env
$ echo "BRIDGE_NICKNAME=WTBr$(cat /dev/urandom | tr -cd 'qwertyuiopasdfghjklzxcvbnmMNBVCXZLKJHGFDSAQWERTUIOP0987654321'|head -c 10)" >> .env
$ echo "WEBTUNNEL_ENABLE_ADDITIONAL_VARIABLES=1" >> .env
$ echo "WEBTUNNELV_AssumeReachable=1" >> .env
The solution does not use IPv6 for tor connections, but this might be achieved differently:
See WebTunnel/Docker: “Unable to find IPv6 address for ORPort” - #2 by atari for explanation.
In general there should be a better working Docker image, this is just dirty fixing making it even harder do understand what is going on…