What do these messages mean?

Support
1

Hello,
When I run the Tor I see the following messages:

...
Jan 21 12:22:13.000 [notice] Bootstrapped 100% (done): Done
Jan 21 12:22:13.000 [warn] Guard Unnamed ($AA7630738F82C4DF26BB8EFF131564DACDEAC64C) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 100/242. Use counts are 21/27. 230 circuits completed, 0 were unusable, 130 collapsed, and 162 timed out. For reference, your timeout cutoff is 237 seconds.
Jan 21 12:22:13.000 [warn] Guard Unnamed ($6E402A413395D0E8794817C3C50C2B1F7DBF1B0E) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 56/265. Use counts are 1/1. 253 circuits completed, 0 were unusable, 197 collapsed, and 203 timed out. For reference, your timeout cutoff is 237 seconds.
Jan 21 12:22:14.000 [warn] Guard anonymous1337 ($BC7BBFBBF4AE5469405591D28BF3EF8071B0F32E) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 47/215. Use counts are 0/0. 207 circuits completed, 0 were unusable, 160 collapsed, and 170 timed out. For reference, your timeout cutoff is 237 seconds.
Jan 21 12:23:17.000 [warn] Guard SupportSeaWatch ($F85CDCD037B3C834D03F046205047C409557A5BC) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 53/174. Use counts are 2/2. 168 circuits completed, 0 were unusable, 115 collapsed, and 129 timed out. For reference, your timeout cutoff is 92 seconds.
Jan 21 12:27:19.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Jan 21 12:27:19.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Jan 21 12:27:19.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Jan 21 12:27:19.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Jan 21 12:27:19.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up.
Jan 21 12:27:19.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Jan 21 12:27:24.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up.
Jan 21 12:27:24.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up.
Jan 21 12:29:38.000 [warn] Guard laeviculus ($A78372EC69D60877AB34F4128FE3499A58DD2C31) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 129/291. Use counts are 30/30. 278 circuits completed, 0 were unusable, 149 collapsed, and 165 timed out. For reference, your timeout cutoff is 100 seconds.
Jan 21 12:33:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
Jan 21 12:33:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jan 21 12:33:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:80. Giving up. (waiting for circuit)
Jan 21 12:33:41.000 [notice] Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)

Why?

Thank you.

2

Hello,
No idea?
The Tor stops and I have to reset it. Do the above and below reports indicate a problem?

Jan 23 00:00:04.000 [notice] Tor 0.4.7.16 opening new log file.
Jan 23 02:58:12.000 [notice] Tor has not observed any network activity for the past 73 seconds. Disabling circuit build timeout recording.
Jan 23 02:58:14.000 [notice] Tor now sees network activity. Restoring circuit build timeout recording. Network was down for 75 seconds during 1 circuit attempts.
Jan 23 03:59:08.000 [notice] Heartbeat: Tor's uptime is 1 day 12:00 hours, with 12 circuits open. I've sent 3.16 GB and received 16.02 GB. I've received 160344 connections on IPv4 and 0 on IPv6. I've made 97 connections with IPv4 and 0 with IPv6.
Jan 23 03:59:08.000 [notice] While not bootstrapping, fetched this many bytes: 345555 (consensus network-status fetch); 490051 (microdescriptor fetch)
Jan 23 03:59:08.000 [notice] Average packaged cell fullness: 78.262%. TLS write overhead: 2%
Jan 23 09:28:10.000 [notice] Interrupt: exiting cleanly.
Jan 23 09:28:10.000 [notice] Tor 0.4.7.16 opening log file.
Jan 23 09:28:10.839 [notice] We compiled with OpenSSL 300000b0: OpenSSL 3.0.11 19 Sep 2023 and we are running with OpenSSL 300000b0: 3.0.11. These two versions should be binary compatible.
Jan 23 09:28:10.845 [notice] Tor 0.4.7.16 running on Linux with Libevent 2.1.12-stable, OpenSSL 3.0.11, Zlib 1.2.13, Liblzma 5.4.1, Libzstd 1.5.4 and Glibc 2.36 as libc.
...
Jan 23 10:51:04.000 [warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed].
Jan 23 10:56:13.000 [warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed]. [100 similar message(s) suppressed in last 360 seconds]
Jan 23 11:02:38.000 [warn] Rejecting SOCKS request for anonymous connection to private address [scrubbed]. [14 similar message(s) suppressed in last 420 seconds]
3

“Rejecting SOCKS request for anonymous connection to private address [scrubbed]”

What I think is happening here is that your computer is attempting to communicate to a private (non public facing) IP address. For example, the Wi-Fi router you are connected to is usually 192.168.1.X

So I believe what’s happening is that you are trying to route such requests over Tor, which is impossible (it should be a direct device → router connection).

4

Hello,
Tor is behind a firewall, but it works as NAT, which means it has direct access to the Internet and no policy is applied to it!
How about the following message:

Tried for 120 seconds to get a connection to [scrubbed]:443. Giving up. (waiting for circuit)
5

It seems that it’s timed out connecting to a specific IP.

Try getting a new circuit; and make sure the service that you are connecting to is online and not just dropping all Tor packets.

6

Hello,
Thanks again.
How to get a new circuit? Should I use the systemctl restart tor command?

7

Honestly?

I have no idea. You’d have to ask somebody more knowledgeable

8

Hello,
When I use the bridge, I see the following message:

Application request when we haven't used client functionality lately. Optimistically trying known bridges again.

What does it mean?