A Docker container that provides a rotating proxy service using multiple Tor circuits for IP rotation.
Rotating TOR proxy is a Docker container that sets up a rotating proxy service using multiple Tor circuits. It solves the problem of IP-based blocking or rate limiting by providing a pool of different IP addresses through a single endpoint, making it ideal for anonymous web scraping or testing.
Developers and researchers who need to rotate IP addresses for web scraping, data collection, or testing applications without being blocked by IP-based restrictions.
It offers an easy-to-deploy, self-contained solution with built-in load balancing and monitoring, eliminating the need to manually manage multiple Tor instances while ensuring reliable IP rotation.
Rotating TOR proxy with Docker
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.
Provides a ready-to-use Docker container with simple build and run commands, as shown in the README with 'docker run -d -p 5566:5566 -p 4444:4444', abstracting the complexity of managing multiple Tor instances.
HAProxy offers one endpoint (port 5566) for clients to connect to, load-balancing across all Tor proxies, simplifying client configuration as illustrated in the architecture diagram.
Includes a web-based HAProxy stats page accessible via port 4444, allowing real-time performance monitoring without additional setup, mentioned in the 'monitor' section.
Rotates through multiple Tor circuits to provide different IP addresses per request, ideal for bypassing IP-based rate limits, as highlighted in the key features.
Relies on the Tor network, which is known for high latency and slow speeds, making it unsuitable for time-sensitive or high-throughput applications like fast web scraping.
Uses Polipo for HTTP-to-SOCKS translation, which is an older, less-maintained project, potentially leading to compatibility issues or security concerns as noted in the README.
Only supports HTTP proxy protocol via HAProxy and Polipo, not direct SOCKS, which may restrict clients that require SOCKS proxies or advanced proxy features.
Offers minimal configuration through environment variables (e.g., tors=25), with no documentation for advanced HAProxy or Tor settings, limiting customization for complex use cases.