I tried now with policy outgoing forward and Tor did not started, so the problem has another reason, it seems that the Tor addon is broken with build 201
11:04:33 Tor[11499]: Catching signal TERM, exiting cleanly.
May 8 11:04:40 Tor[7790]: We compiled with OpenSSL 30600010: OpenSSL 3.6.1 27 Jan 2026 and we are running with OpenSSL 30600010: 3.6.1. These two versions should be binary compatible.
May 8 11:04:40 Tor[7790]: Tor 0.4.8.21 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.6.1, Zlib 1.3.1.zlib-ng, Liblzma 5.8.2, Libzstd 1.5.7 and Glibc 2.43 as libc.
May 8 11:04:40 Tor[7790]: Tor can’t help you if you use it wrong! Learn how to be safe at
May 8 11:04:40 Tor[7790]: Read configuration file “/usr/share/tor/defaults-torrc”.
May 8 11:04:40 Tor[7790]: Read configuration file “/etc/tor/torrc”.
May 8 11:04:40 Tor[7790]: ControlPort is open, but no authentication method has been configured. This means that any program on your computer can reconfigure your Tor. That’s bad! You should upgrade your Tor controller as soon as possible.
May 8 11:04:40 Tor[7790]: Opening Socks listener on 127.0.0.1:9060
May 8 11:04:40 Tor[7790]: Opened Socks listener connection (ready) on 127.0.0.1:9060
May 8 11:04:40 Tor[7790]: Opening Control listener on 127.0.0.1:9051
May 8 11:04:40 Tor[7790]: Opened Control listener connection (ready) on 127.0.0.1:9051
May 8 11:04:40 Tor[7790]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
May 8 11:04:40 Tor[7790]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
May 8 11:04:40 Tor[7790]: Set list of supported TLS groups to: ?*X25519MLKEM768 / ?SecP256r1MLKEM768 / *P-256:?X25519:P-224
May 8 11:04:40 Tor[7790]: Bootstrapped 0% (starting): Starting
May 8 11:04:41 Tor[7790]: Starting with guard context “default”
after this nothing happens any more, only heartbeat messages in log.