Tor's control port could not be reached

Support
1

// Imgur: The magic of the Internet

2

Thank you for reporting this.

This needs some more information.

Is this by chance a very slow machine?

Does this happen on a freshly installed and verified Whonix-Gateway?

Have you applied any changes?

Does this persist after restarting Tor? (“sudo service tor restart”)

Does this persist after reboot?

This test is checking if a Tor SocksPort can be reached. Essentially it is running.

The following is expected:

curl: (22) The requested URL returned error: 501 22

What happens if you manually run the following?

Eventually the timeout is too short.

What happens if you manually run the following?

3

Thanks a lot for the reply! Unfortunately or rather fortunately the error didn’t come up when I started the gateway today. I should have waited a bit myself before asking for help. Just in case I wanted to answer the questions:

  1. The machine’s specs are: Intel Core i5-2410M (2.3 GHz), 4 GB DDR3, NVIDIA GeForce GT 525M (1024 MB) and running windows 7.
  2. Yes, this is happening in a brand new installation.
  3. I’ve applied 0 changes.
  4. Can’t tell if Tor restart would’ve fixed it.
  5. It does not persist after reboot!
  6. The expected response happened when I ran both commands.

Thanks again.

4

I am happy about the report, I think about raising the timeout.

This remains a mystery. I can only tell you, that your system is most likely not too slow. Unless it was under heavy load at that time (Installing other software, virus scanning, search index etc.).

5

Yeah, it pretty fast. I gave each VM 3 gigs of ram. Wasn’t doing anything other than following the wiki install guide at the time.

6

Maybe my best bet is to re-install qubes. Then re-install whonix and go slowly. I’ll try that and update you in the near future.

7

I don’t think the issue of this thread is related to Whonix Forum.