Again Tor's Control Port could not be reached!

Support
1

Hello! On my computer I have VPN running throw nekobox application. On Whonix Geteway I connect to Tor with a bridge
On Gateway there is internet connection. I can run apt update. Result whonixcheck is:

[gateway user ~]% whonixcheck
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 0 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 2 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 4 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 6 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 8 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 10 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 12 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 14 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 16 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Tor Connection Result:
- Connecting for 18 seconds. | 100 % done. 
- Tor Circuit: established.
- Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
- Timesync status: not done.
- sdwdate reports: Initial time fetching in progress...
- onion-time-pre-script reports: 
__ ### START: ### /usr/libexec/helper-scripts/onion-time-pre-script
__ Status: Subsequent run after boot.
__ Static Time Sanity Check: Within minimum time 'Tue Nov  5 00:00:00 UTC 2024' and expiration timestamp 'Tue May 17 10:00:00 UTC 2033', ok.
__ Tor reports: NOTICE BOOTSTRAP PROGRESS=100 TAG=done SUMMARY="Done"
__ Tor circuit: established
__ Tor Consensus Time Sanity Check: Clock within consensus parameters consensus/valid-after 2025-05-07 14:00:00 and consensus/valid-until 2025-05-07 17:00:00.
__ Conclusion: Tor already reports circuit established.
__ ### END: ### Exiting with exit_code '0' indicating 'success'.
[INFO] [systemcheck] Connected to Tor.
[INFO] [systemcheck] Whonix is produced independently of, with no guarantee from, The Tor Project. Whonix is a research project. https://www.whonix.org
[INFO] [systemcheck] Whonix APT Repository: Enabled.
When the Whonix team releases BOOKWORM updates,
they will be AUTOMATICALLY installed (when you run apt-get dist-upgrade)
along with updated packages from the Debian team. Please
read https://www.whonix.org/wiki/Trust to understand the risk.
If you want to change this, use:
    sudo repository-dist
[INFO] [systemcheck] Debian Package Update Check: Checking for software updates via apt-get... ( Documentation: https://www.whonix.org/wiki/Update )
[INFO] [systemcheck] Debian Package Update Check Result: No updates found via apt-get.
[INFO] [systemcheck] Please donate!
   See: https://www.whonix.org/wiki/Donate

But on Workstation there is not internet connection. Result whonixcheck is:

workstation user ~]% whonixcheck
[INFO] [systemcheck] Tor Connection Result:
Tor's Control Port could not be reached. Attempt 1 of 5. Could be temporary due to a Tor restart. Trying again...
[INFO] [systemcheck] Tor Connection Result:
Tor's Control Port could not be reached. Attempt 2 of 5. Could be temporary due to a Tor restart. Trying again...
[INFO] [systemcheck] Tor Connection Result:
Tor's Control Port could not be reached. Attempt 3 of 5. Could be temporary due to a Tor restart. Trying again...
[INFO] [systemcheck] Tor Connection Result:
Tor's Control Port could not be reached. Attempt 4 of 5. Could be temporary due to a Tor restart. Trying again...
[ERROR] [systemcheck] Tor Connection Result:
Tor's Control Port could not be reached!

Troubleshooting:
- Confirm that Whonix-Gateway is running.
- Run systemcheck on Whonix-Gateway and confirm success.
- If you're running multiple Whonix-Workstations simultaneously, confirm that separate IP addresses are configured (see https://www.whonix.org/wiki/Multiple_Whonix-Workstations).
- Rerun systemcheck here in this Whonix-Workstation.

(Technical information:)
(tor_circuit_established_check_exit_code: 255)
(tor_bootstrap_timeout_type: )
(tor_bootstrap_status: )
(check_socks_port_open_test: 56)
(Tor Circuit: not established)
zsh: exit 1     whonixcheck

In Nyx there is message:

[WARN] Socks version 71 not recognized. (This port is not an HTTP
 │   proxy; did you want to use HTTPTunnelPort?)

Please, help solve this problem!

1 Like
2

Which virtualizer?

Where exactly? Host operating system? Whonix-Gateway? Whonix-Workstation?

What?

1 Like
3

VirtualBox

On host OS, Windows 11. VPN with protocols VLESS+Reality. For connection to VPN I use Nekobox.

1 Like
4

This software is apparently breaking the inter VM networking between Whonix-Workstation and Whonix-Gateway.

Consider this unsupported.

1 Like
5

Tell me, please, which virtualizer I can use then. Or you are talking about NekoBox?

1 Like
6

In case of:

No known solutions. Unsupported.

1 Like
7

Without VPN I get the same - Tor’s Control Port could not be reached!

1 Like
8

Most likely a prior installation of the VPN software has broken the internal networking of VirtualBox.

Whonix is functional for 1000s of users. There is no bug Whonix’s source code that could be fixed.

A third-party software is breaking VirtualBox internal networking.

You’re asking in the wrong place.

1 Like
9

OK. Suppose. But I don’t install Nekobox. It’s running without installation. When it isn’t running there isn’t additional network adapters in Device manager. Maybe is there another problem?

1 Like
10

This doesn’t happen on a normal Windows installation. This doesn’t happen on a normal Linux operating system.

Once you install special VPN software or firewalls on the host operating system that disrupt virtualizer internal networking, you need to repair it.

How to repair it? I doubt anyone here knows. You’re asking in the wrong place.

Not only Whonix would be broken but any internal networking between any non-Whonix VMs.

Testing with a Debian VM would be good, but setting up internal networking isn’t trivial to test. The end result of the test would probably be “also non-Whonix VMs internal networking is broken”, and not any closer to a solution.

That doesn’t necessarily mean everything is good. It could also be something else such as a device driver; firewall; other unknowns.

1 Like