Tor in virtual machine - 502 bad gateway

I'm trying to run Tor in virtual machine. It used to work, but now when I try to access sites I get "502 bad gateway" error from Privoxy instead of requested site. I tried fixing time to correct one with date command but I still get 502 error. I use Virtualbox, Linux guest, and Tor+Privoxy setup.

3

3 Answers

Check the virtual machine can access the internet by pinging then using wget/curl to get a webpage, since the log suggests that is where the error is. If you can't then it's a networking problem with the virtual machine and you'll need to make sure the Virtualbox network is correctly configured and that the virtual machine is getting an ip address correctly.

If the virtual machine can connect then it's likely a config issue with Tor or Privoxy. Try bypassing Privoxy by using Tor directly on the virtual machine - torify wget should do that.

Try going to Google normally without Tor.

If you can do this, it is possible that your ISP is blocking TOR or the page you are visiting is just filtered at the other end.

Also, if you can visit Google normally, it means that this problem is related to Tor itself and nothing to do with being inside a virtual machine.

2

If you are being blocked from establishing a connection with the Tor network try using a bridge. Basically bridges are secret lists of Tor servers and since they are released only a few at a time not all of them can be blocked. See here.

Is it possible to try using Tor on the host machine, or on an entirley different machine using the same network connection? If this succeeds it would rule out any posibility of your network blocking Tor.

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

You Might Also Like