just 3 steps:
Run a VM/box dedicated to Tor
Route all the rest of the traffic through it - except the Tor node one
Do not confirm your phone, e.t.c... = keep a digital hygiene up
And it will work for sure
Yes so far you are correct.
If your only threat model is your university, you may use VPN/ssh tunneling whatever, which may be faster than tor and wont use so much resources for such a simple task.
If your threat model includes more than that, you might need tor.
Well, it looks like they're using a Cloudflare or a similar service to do tor blocking and CDN service. They do track you as you're using their service, so - discard them, there's nothing more you can do from your side
This seems like the letterboxing feature witch is used to avoid fingerprinting.
Try turning privacy.resistFingerprinting.letterboxing to false to get rid of it.
That is all I know about the letterboxing feature. Hope this helps.
Well, you don't need anything except the NGinx and tor running on the same box: in nginx server block you utilize the include ability - so you will have two server blocks for defining listening address - a clearnet IP for open web and 127.0.0.7 for Tor - and separate logging, separate HTTPS certificates with corresponding host names in them to avoid ...
Tailscale is not the right choice to do it out of the box and you need it vice versa: you need to use OpenVPN from your NAT'ed box to the VPS and the client here should be a NAT'ed box. After that just forward the port VPS->NATed via static OpenVPN internal IP's and make the NAT for tor process user through the VPN tunnel. Then self-check will succeed and ...
Check your tb logs - the Tor Browser Bundle has it's own tor supplied with it and until it's 100% bootstrapped - neither a side app(burpsuite in your case) nor the tb itself will not work. The Tb's Tor log has a full answer for your problem, it's nowhere else to look
Try setting the Address option in your torrc file to the public address of your VPS. From the tor man page:
The IPv4 address of this server, or a fully qualified domain name of this server that resolves to an IPv4 address. You can leave this unset, and
Tor will try to guess your IPv4 address. This IPv4 address is the one used to ...
Please note that Tor Browser comes bundled with it's own tor which is separate from the little-t-tor you're running on the command-line.
To use bridges with little-t-tor you will have to manually edit your torrc (located at /etc/tor/torrc) and add the following lines:
Bridge <bridge address>
Also see: https://support.torproject.org/...
I realize that the question was asked about a year ago, but I will respond hoping that it would be useful for someone given the ongoing v2 onion services deprecation.
Assuming you already created a version 3 address i.e in torrc add these lines:
HiddenServicePort <virtual port> <target-address>...
I found article on website about tor proxy https://itgala.xyz/nginx-reverse-proxy-to-onion-site-in-tor-network/
I wanted to mirror any tor website to my tor site
My Nginx config: /etc/nginx/sites-enabled/hy-reverse
listen 127.0.0.1:80 default_server;
index index.html index....