a lightweight, secure by default HTTP, HTTPS and SOCKS proxy server, ready in minutes
3proxy is a lightweight, tiny proxy server providing HTTP and HTTPS forward proxying and a SOCKS4/5 proxy in a single small daemon. It gives applications a controlled, authenticated egress point: send traffic through a single hardened hop, add a SOCKS proxy for tools that need one, or build a small private forward-proxy tier. This image delivers it installed and running under systemd, so a working proxy endpoint is listening within minutes of launch with no compilation or configuration.
The cloudimg image is secure by default and deliberately not an open relay: a unique proxy username and password are generated on first boot and never baked into the image, proxy authentication is enforced so anonymous requests are refused, and access is restricted to private client ranges with a deny-all default. HTTPS CONNECT is limited to standard TLS ports, the OS ships fully patched with unattended security updates, and every deployment is backed by a paired step-by-step guide and 24/7 cloudimg support.
This is a repackaged open source software product wherein additional charges apply for cloudimg support services.
3proxy is a lightweight, tiny proxy server that provides HTTP and HTTPS forward proxying and a SOCKS4/5 proxy in a single small daemon. This image delivers it fully installed and running under systemd, so a working proxy endpoint is listening within minutes of launch, with no manual compilation and no configuration required to get started. The HTTP and HTTPS forward proxy listens on port 3128 and the SOCKS proxy on port 1080, both managed by systemd for automatic restarts and clean logging.
Unlike a bare deployment, this image is configured to be secure by default and is deliberately not an open relay. There is no default password baked into the image: a unique proxy username and password are generated on this instance's first boot and never shipped inside the image. Proxy authentication is enforced, so an anonymous or wrong-password request is rejected with HTTP 407 and carries no traffic. The default access control list allows authenticated clients only from loopback and the private RFC1918 ranges, followed by a deny-all rule, and HTTPS CONNECT tunnelling is restricted to the standard TLS ports so the proxy cannot be abused to reach arbitrary destinations. The operating system ships fully patched with unattended security updates enabled.
Use 3proxy to give applications a controlled, authenticated egress point, to reach the internet through a single hardened hop, to add a SOCKS proxy for tools that need one, or to build a small private forward-proxy tier. To serve clients outside the instance, widen the access control list to your own client CIDR in the configuration file and open the matching port in your security group, as described in the deployment guide. The current release available is 3proxy 0.9.7.
This is a repackaged open source software product with additional charges for cloudimg support services. 3proxy is distributed under a BSD-style permissive license. cloudimg is not affiliated with or endorsed by the 3proxy project. All product and company names are trademarks or registered trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.