After fresh installation, i would open the Tor Proxy, but it doesn’t work, so he opens the Proxy Port as configured at 0.0.0.0:9050 but the Start in the logs ends here —>>
Apr 12 09:28:00 Tor[4441]: Catching signal TERM, exiting cleanly.
Apr 12 09:28:20 Tor[16103]: 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.
Apr 12 09:28:20 Tor[16103]: 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.42 as libc.
Apr 12 09:28:20 Tor[16103]: Tor can’t help you if you use it wrong! Learn how to be safe at Tor Browser best practices - Security - Tor Browser — Tor
Apr 12 09:28:20 Tor[16103]: Read configuration file “/usr/share/tor/defaults-torrc”.
Apr 12 09:28:20 Tor[16103]: Read configuration file “/etc/tor/torrc”.
Apr 12 09:28:20 Tor[16103]: 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.
Apr 12 09:28:20 Tor[16103]: You specified a public address ‘0.0.0.0:9050’ for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don’t allow this unless you have a good reason.
Apr 12 09:28:20 Tor[16103]: Opening Socks listener on 0.0.0.0:9050
Apr 12 09:28:20 Tor[16103]: Opened Socks listener connection (ready) on 0.0.0.0:9050
Apr 12 09:28:20 Tor[16103]: Opening Control listener on 127.0.0.1:9051
Apr 12 09:28:20 Tor[16103]: Opened Control listener connection (ready) on 127.0.0.1:9051
Apr 12 09:28:20 Tor[16103]: Parsing GEOIP IPv4 file /usr/share/tor/geoip.
Apr 12 09:28:20 Tor[16103]: Parsing GEOIP IPv6 file /usr/share/tor/geoip6.
Apr 12 09:28:20 Tor[16103]: Set list of supported TLS groups to: ?*X25519MLKEM768 / ?SecP256r1MLKEM768 / *P-256:?X25519:P-224
Apr 12 09:28:20 Tor[16103]: Bootstrapped 0% (starting): Starting
Apr 12 09:28:21 Tor[16103]: Starting with guard context “default”
After this it repeats every single hour
Apr 12 13:26:20 Tor[22634]: Tor has been idle for 3600 seconds; assuming established circuits no longer work.
and every 8 hours
Apr 14 10:26:20 Tor[22634]: Heartbeat: Tor’s uptime is 0:00 hours, with 0 circuits open. I’ve sent 0 kB and received 0 kB. I’ve received 2 connections on IPv4 and 0 on IPv6. I’ve made 0 connections with IPv4 and 0 with IPv6.
I would call it time-sheet fraud 
Infos: Fresh install and ipfire Firewall outgoing and forward at blocked. NAT enabled
Same happens if i start the proxy at 172.16.0.1 my ipfire address
Any solutions ?
Best regards