Hello bridge operators, During yesterday's upgrade of our WebTunnel docker image, some bridges stopped working due to an operating system issue[1]. Only WebTunnel operators using our official Docker image are affected. If your bridge is affected and you don’t apply this fix, it will remain non-functional and users will not be able to connect. You need to take action now! ### How to check if your bridge is affected Run the command: `docker ps` If your WebTunnel container is stuck in a restart loop (shows `Restarting (1)` or similar message), then your bridge needs fixing: ``` thetorproject/webtunnel-bridge:latest "/usr/local/bin/star…" 22 hours ago Restarting (1) 21 seconds ago webtunnelBridge5a35b7dd47c6 containrrr/ ``` ### How to fix your WebTunnel docker bridge 1. List your Docker volumes: ``` docker volume list ``` 2. Identify the persistent volume for Tor, then run (adjust the volume name accordingly): ``` docker run --rm -it -v root_webtunnel-tor-state:/var/lib/tor debian chown -R 100 /var/lib/tor ``` 3. Restart your bridge: ``` docker compose up -d ``` If you need help, please reach out to us on irc #tor-relays (irc.oftc.net) or matrix: https://matrix.to/#/#tor-relays:matrix.org. Thank you for running bridges! gus [1] https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/webtu... -- The Tor Project Community Team Lead