<no warranty for nothing - works for me^^>
First of all, this will not stop the spamming your logs, there will be new/other warnings but IPv6 should work (at least it did for me)…
Assumption: You used these instructions Tor Project | WebTunnel Docker setup
Your .env
should have these additional lines (and you may remove the GENEDORPORT
-line (number 4 from instructions):
WEBTUNNEL_ENABLE_ADDITIONAL_VARIABLES=1
WEBTUNNELV_AssumeReachable=1
WEBTUNNELV_ORPort=[::1]:auto IPv6Only
docker-compose.yml
should be adapted like this (I removed watchtower):
networks:
wtb_net:
enable_ipv6: true
driver: bridge
ipam:
driver: default
config:
- subnet: 2001:db8:1::/64
gateway: 2001:db8:1::108
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
- WEBTUNNELV_ORPort=$WEBTUNNELV_ORPort
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'
networks:
wtb_net:
ipv6_address: 2001:db8:1::256
volumes:
webtunnel-tor-state:
Explanation:
ORPort
in environment is set to 127.0.0.1:auto
→ It should not be reachable from outside (see).
Also via WEBTUNNELV_ORPort=[::1]:auto
tor is instructed to use IPv6.
So consequently the line - '$GENEDORPORT:$GENEDORPORT'
is removed, because ORPort will not be exposed.
Additionally a new network with IPv6 is defined and started, when the container is running. This might need to be adapted to a different subnet, if you have other IPv6 containers on your host.