You have a simple nginx webserver and it is listening on http port 80 for mywebsite.com.
You set up tor to also listen externally on virtual port 80 as a onion service for mywebsiteabcxyz.onion.
This can all live on the same web server at the same time. No reverse proxy is required. The key is that tor will always listen for a virtual onion service port ...
@lmen is probably talking about Tor Proxy Buildpack for Heroku, it can setup Tor on a heroku node with socks5 and control port available (They can be configured in the environment values).
All you need to do is run
$ heroku buildpacks:add https://github.com/iamashks/heroku-buildpack-tor-proxy.git
And it will automatically setup a proxy that you can use at ...
The flag StaleDesc was developed throught a proposal. Anyone can send in a proposal to improve the Tor protocol. The specific proposal has the number 293 with the title "Other ways for relays to know when to publish". The implementation was tracked in ticket #26770.
Authorities recognize that a relay descriptor is too old and assign this flag. A relay ...
Tor cannot help you perform a SYN scan. Tor anonymizes client TCP connections and a SYN scan does not establish a full TCP connection. In this case nmap does not use your SOCKS proxy at all as it does not establish any TCP connections.
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:
ProxyCommand socat STDIO SOCKS4A:<tor socks hostname or IP>:%h:%p,socksport=9050
This should also be the only change needed for git ssh ...
Most of these questions are far too broad, but I'll do my best.
Setting an onion service is easy. You install the Tor service, tell it to use port 80, get your new onion address and start a web server. That's easy. Here is the official guide
if there is an extising guide from buying the server through to server
coding and other softwhere pointers?