Serve traffic / content to real users, not bots.Stop bots from scraping your content or bots spamming your website.Prevent users from abusing promotional offers / multiple sign-ups / affiliate abuse.

Protect your site from crawlers that steal your content.Protect your site from automated hacking attempts such as XSS, SQLi, brute force attacks, application scanning and many others.Greatly reduce fraud on e-commerce sites (anti-fraud).Use this command curl -socks5 :9050 to test connection to Tor service from other computer on your network.Allow TCP port 9050 through the firewall if necessary.# can access your SocksPort may be able to learn about the connections # all (and only) requests that reach a SocksPort. # Entry policies to allow/deny SOCKS requests based on IP address. #SocksPort 9050 # Default: Bind to localhost:9050 for local connections. # as a relay, and not make any local application connections yourself. Set 'SocksPort 0' if you plan to run Tor only # Tor opens a socks proxy on port 9050 by default - even if you don't The /etc/tor/torrc file should look like this after adding the above entries.

which means that any IP in the 192.168.56.X range will be accepted by Tor. If your host has, for example, an IP 192.168.56.100 add an entry according to that value. Without it, Tor will not be accessible outside the server (localhost) that runs it. listens for connections from other network interfaces and not just the local one (127.0.0.1). Here is my answer based on the responses of my forum colleagues and adding some more guidelines.

Check tor proxy