Then I had a tor connection, and hadn’t current task
I repeated following commands:
sudo rm /usr/local/etc/torrc.d/40_tor_control_panel.conf
sudo rm /usr/local/etc/torrc.d/50_user.conf
sudo service tor@default restart
before
/usr/local/etc/torrc.d/40_tor_control_panel.conf
DisableNetwork 1
/usr/local/etc/torrc.d/50_user.conf
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy
Bridge obfs4 95.216.209.193:7790 B7A195523AC85625E62E308D5DD84E74C7C5F276 cert=hNM+1FI4iviImkAY9W2E2oHxM/+Ex4ajlOOQ0nMaBzhEBRXTumG5NXXOvnnHdmS8PrfgFQ iat-mode=0
UseBridges 1
DisableNetwork 0
after
/usr/local/etc/torrc.d/40_tor_control_panel.conf
DisableNetwork 1
/usr/local/etc/torrc.d/50_user.conf
And what’s the result?
Nothing has changed, tor doesn’t work
When tor creates the above configuration file, after deleting it it becomes empty, if I’ll add Bridges (Tor is censored in my country) the same problem occurs, 2% loading
Wait, What? Everything seems to be in order, after testing I’ll write here
Hi, Patrick, if you’re still here. It worked properly for a few days, but a couple hours ago I encountered the same problem, then I repeated step by step all the things I have done to solve this problem
First I entered the following commands in virtual console:
sudo systemctl stop gdm3
sudo rm /var/cache/anon-base-files/first-boot-skel.done
sudo /usr/libexec/helper-scripts/first-boot-skel
sudo systemctl restart gdm3
then I entered these in console:
sudo rm /usr/local/etc/torrc.d/40_tor_control_panel.conf
sudo rm /usr/local/etc/torrc.d/50_user.conf
sudo service tor@default restart
I’m listening for any changes in /usr/local/etc/torrc.d
.
After sudo service tor@default restart
nothing changes.
Connecting status in anon-connection-wizard is 5% at maximum, after executing later /usr/local/etc/torrc.d/40_tor_control_panel.conf
file creates. I manually create 50_user.conf
and fill it out with these instructions:
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy
Bridge obfs4 * iat-mode=0
UseBridges 1
DisableNetwork 0
Then I retry sudo service tor@default restart
Then I come to the starting point. 2% hang.
So is this a new issue or still the same issue?
The old issue was, that Tor is terminating due to config issues. Does
Tor keep running now but stuck at 2%? That would be technically a
different issue. Important to know so we’re not talking past each other.
KeeXago via Whonix Forum:
Hi, Patrick, if you’re still here. It worked properly for a few days, but a couple hours ago I encountered the same problem, then I repeated step by step all the things I have done to solve this problem
First I entered the following commands in virtual console:
sudo systemctl stop gdm3 sudo rm /var/cache/anon-base-files/first-boot-skel.done sudo /usr/libexec/helper-scripts/first-boot-skel sudo systemctl restart gdm3
Don’t worry about resetting Xfce desktop settings. This is completely
unrelated here. Tor doesn’t interact with Xfce or any desktop settings.
then I entered these in console:
sudo rm /usr/local/etc/torrc.d/40_tor_control_panel.conf sudo rm /usr/local/etc/torrc.d/50_user.conf sudo service tor@default restart
I’m listening for any changes in
/usr/local/etc/torrc.d
.
Aftersudo service tor@default restart
nothing changes.
What doesn’t change? The Tor process now keeps running at least?
First thing to confirm is if Tor process keeps running.
Connecting status in anon-connection-wizard is 5% at maximum, after executing later
/usr/local/etc/torrc.d/40_tor_control_panel.conf
file creates. I manually create50_user.conf
and fill it out with these instructions:ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy Bridge obfs4 * iat-mode=0 UseBridges 1 DisableNetwork 0
Then I retry
sudo service tor@default restart
Then I come to the starting point. 2% hang.
Did you really use *
or just redact the IP/port of the bridge? Using
*
is invalid syntax, would fail. Redacting the bridge IP/port would be
good but please mention.
If the Tor process keeps running but connection is stuck at 5% then the
following wiki page applies:
Yes
Sure, I use the correct bridge
5% only if I do not use bridges, 2% with them.
Also I don’t know how to detect Tor process status, could you mention here? I guess it’s the same problem.
When I siad What doesn’t change? What I meant was: 50_user.conf
didn’t create
Run systemcheck.
systemcheck would tell you if Tor wasn’t running.
systemcheck
Alternatively:
- Log Analysis
- Tor not running
- Daemon Status
-
sudo systemctl status tor@default
-
- Potential Solutions Beyond Whonix!
It’s automatically created.
(Technical details: https://github.com/Whonix/anon-gw-anonymizer-config/blob/master/lib/systemd/system/anon-gw-anonymizer-config.service)
Hello. Due to the fact that TOR stopped working due to censorship. The same problem occurred when connecting via bridges.
After these actions the problem did not disappear.
Systecheck:
WARNING: Tor Check Result: Tor is disabled. Therefore you most likely can not connect to the internet.
(Debugging information: Could not find DisableNetwork 0 in Tor config.)
Please close this window and enable Tor using Anon Connection Wizard!
Start Menu -> System -> Anon Connection Wizard
or in Terminal: sudo setup-dist
or manually (If you know about the public Tor network!) and open /usr/local/etc/torrc.d/50_user.conf with root rights (Start Menu -> System -> Tor User Config) and set:
DisableNetwork 0
Then run systemcheck again.
Did you read the error message and apply what’s said there?
If you write to this file like this and run systemcheck /usr/local/etc/torrc.d/50_user.conf
ClientTransportPlugin obfs4 exec /usr/bin/obfs4proxy
Bridge obfs4 51.81.186.192:41115 7B1A9C4C737DB00E01749803383786165FF599B4 cert=fCX1D+45ApfprlWeWLcyBDj0GvoqOGkevfT7IRFqZOmTJ5rjK7ZkUoc6ei5KJLSyWy+uSA iat-mode=0
Bridge obfs4 185.177.207.137:8443 D6B9EC832A0D9E6A181A62D4D72CC3A9FEDF60CB cert=4Q8yZaa1lzkPmxsbtanABUYaapxko+AoVtsBNoWGC4+YLBCgavxoM3x4Kn+SX3rLVNubDQ iat-mode=0
UseBridges 1
DisableNetwork 0
systemcheck:
ERROR: Tor Connection Result:
systemcheck gave up waiting.
Tor Circuit: not established
Connection 2 % done. Tor reports: NOTICE BOOTSTRAP PROGRESS=2 TAG=conn_done_pt SUMMARY="Connected to pluggable transport"
Possible issues:
- Is the host's internet connection working?
- Whonix-Gateway will need a few moments for bootstrapping the Tor network.
- Do you live in a censored area?
- https://www.whonix.org/wiki/Network_Obstacle
- Tor needs a reasonable correct time to be able to connect.
Recommendations:
Please check, that the time inside this virtual machine (23/09/2024 06:14:48) is correct. (A clock that is slow or fast up to 30 minutes is okay.) If the time is incorrect, please manually fix it.
1. Open a terminal. (Start Menu -> System -> Terminal)
2. Use the manual clock setting tool.
sudo --set-home clock-random-manual-gui
1)
Shut down Whonix and try to get the Tor Browser Bundle from https://www.torproject.org working on your host. If you cannot get the Tor Browser Bundle to work, you will most certainly not get Whonix to work either.
The Tor Browser Bundle is great for testing if you live in a censored area. If you need bridges for the Tor Browser Bundle, you will need them for Whonix as well.
2)
Try again: Start Menu -> System -> systemcheck
or in Terminal: systemcheck
or more verbose in Terminal: systemcheck --verbose --gui --cli
3)
Use Nyx, connection page two, to see if Tor is connected:
Start Menu -> System -> Nyx
or in Terminal: nyx
This can only be debugged by following these instructions:
Connectivity Troubleshooting