Thank you for your reply…
I am not using any VPNs or proxies
Since there is no connection to Tor this requires disabling stream isolation and running command under user
clearnet . But this might not be a benefit here since Tor is able to connect without bridges. Just a reminder user clearnet runs over clearnet.
I have verified the bridges are in fact valid, and capable of being connected to
sudo -u debian-tor tor --verify-config
I ran the command, and it said Configuration was valid.
Do you have
seccomp configured. Meaning do you have
Sandbox 1 configured in your torrc? If so please remove that configm as
seccomp and bridges are not compatible.
I did not have this setting, and I checked all of the torrc and tor conf files on the machine
I have reviewed the issues on this page, and none apply to my situation
Try using a (private) (obfuscated) bridge that uses port 80 or 443 , as these ports are mostly used for web browsing and therefore usually unblocked.
You may also want to try new bridges even if you are already using port 80, 443 bridges. If the new bridges don’t work try connecting at a later time since Tor network congestion could also be causing this.
I was able to connect via clearnet, so I dont think this is the problem…
The error in arm is “general SOCKS server failure”, sorta vague, so im not sure what the issue is
Does the whonix-gateway work out of the box with tor bridges?