As far as I can tell this is done by: Onion-Location: http://2gzyxa5ihm7nsggfxnu52rck2vv4rvmdlkiu3zzui5du4xyclen53wid.onion/index.html header when accessing https:///www.torproject.org. The header is ...

While marked answer is 100% correct I use a bit different approach. For ssh connections using OpenSSH client I utilze ProxyCommand for *.onion sites in the following way: Host *.onion ...

According to man curl: --socks5 <host[:port]> Use the specified SOCKS5 proxy - but resolve the host name locally. This means --socks5 will use local resolver which CANNOT ...

I've used mkp224o to generate V3 onion addresses.

I think you are looking for NoAdvertise and NoListen flags. The manual says: ORPort [address:]PORT|auto [flags] Advertise this port to listen for connections from Tor clients and servers. ...

Depending on the tor version it is either hidden service v2 or v3 which is the default. And I think it is v3 in your case. Try putting: HiddenServiceVersion 2 in your hidden service definition and ...

I guess the easiest way would be one of: Use separate port number for each hidden service and have your server listen on all of them; Use separate ip address on loopback / dummy device for each ...

As far as I remember shallot is used to generate custom keys and service names for version 2 of hidden services and you are requesting: HiddenServiceVersion 3 Remove the above mentioned line and it ...

Apparently tor changed the default for HiddenServiceVersion from 2 in version 0.3 to 3 in version 0.4. Please check man page and use HiddenServiceVersion 2 as necessary to allow access from older tor ...

protonmail is accessible through their own onion site: https://protonirockerxow.onion/

The application is under 32-bit, 64-bit or 32/64-bit link, depending on OS. (sig) contains only signature of the application, for integrity checking purposes.

Could you check your /etc/hosts for entry starting with ::1 for localhost? If you have it, please try: curl --socks5-hostname 127.0.0.1:9050 https://check.torproject.org You can also try adding SOCKS ...

It has just happened to me and tor gave me useful piece of information in logs: Your server (xxx.xxx.xxx.xx:0) has not managed to confirm that its DirPort is reachable. Relays do not publish ...

If you are trying to setup IPv6 only relay then forget about it - it WILL NOT work. See A Tor relay operators IPv6 HOWTO for more. Specifically the above page says: There is currently no way of ...

If I were to guess I would say this is AccountingMax and its counterparts at work. Many VPS servers (where some individuals run tor relays) limit transfer per accounting period (usually month). This ...

This looks like something to use socat, not iptables. You need to employ socat on server1 to listen on specific port and forward traffic to server2 through tor. Something along the lines: socat TCP-...

Why don't you just use tor for your thunderbird as below: Make sure "Proxy DNS" is checked.

This IP address doesn't respond to pings and any connection attempts on TCP port 443. It is either down, firewalled or recommissioned for other purpose (as nmap reports TCP ports 2000 and 5060 as ...

Could you decide if you want it without (title) or with (body) tor browser? Anyway, I would configure SOCKSPort in tor and configure my browser to use it. Proxy autoconfig could be very helpful here, ...

Try to use full path to your ssh copy like this: torify /tmp/ssh user@remotemachine torsocks /tmp/ssh user@remotemachine

There are two possibilities I know of which may cause this problem: Tor is running as non-root user and permissions on /var/lib do not allow that user to create directory. As you tried to fix it by ...