-1
Daily
5,600
stars
941
forks
127
watchers
79
prs
1,180
issues
41
releases
README
3APA3A 3proxy tiny proxy server
(c) 2002-2026 by Vladimir '3APA3A' Dubrovin
Repository
Branches
- Master (current/latest) branch - 3proxy 1.0
- 0.9 (LTS) branch - 3proxy 0.9.9.x
- Devel branch - 3proxy 1.1 (development, don't use it in production)
- Experimental branch - 3proxy 2.0 (experimental, don't use it)
Binaries (deb / rpm / Windows zip)
https://github.com/3proxy/3proxy/releases
Package repository (apt / dnf)
Signed apt and dnf repositories are published at https://3proxy.org/repo/ in
two channels: current (master) and lts (0.9 branch).
Debian 12 and Ubuntu 22.04 or newer:
sudo curl -fsSL https://3proxy.org/repo/3proxy-release-key.asc \
-o /usr/share/keyrings/3proxy.asc
sudo tee /etc/apt/sources.list.d/3proxy.sources /path/to/local/config/directory/3proxy.cfg
podman run --read-only -p 3129:3129 -v /path/to/local/config/directory/3proxy.cfg:/etc/3proxy/3proxy.cfg --name 3proxy.full 3proxy.full
use log without pathname in config to log to stdout.
plugins are located in /usr/local/3proxy/libexec (/libexec for chroot config) and since 0.9.6 symlinked by /lib and /lib64 in both chroot and non-chroot configurations, so no full path is required in plugin command. Use e.g. plugin SSLPlugin.ls.so ssl_plugin. SSLPlugin is supported since 0.9.6. Some proxy types (e.g. SOCKSv5 UDPASSCOC, SOCKSv5 BIND functionality, ftp proxy) require access to ephemeral port, you may use e.g. --network host mode or -P for docker run.
since 0.9.6 images are distroless (except :busybox) it's recommended to use with read only file system, there are no benefits from chroot. For compatibility, you still can use chroot installation by mounting directory with 3proxy.cfg to /usr/local/3proxy/config.
Busybox image (:busybox):
full with busybox added, to allow sh and few more commands like sed inside container. All libraries are in /lib, so chroot configuration can not use plugins.
Interactive :minimal image:
Dockerfile for "interactive" minimal 3proxy execution, no configuration mounting is required, configuration
is accepted from stdin. Use end command to indicate the end of configuration. Use log for stdout logging.
plugin is not supported, nserver or fakeresolve are mandatory, because system resolver is not supported, no support for RADIUS and IPv6.
Run example:
docker run --read-only -i -p 3129:3129 --name 3proxy docker.io/3proxy/3proxy:minimal
or
docker start -ai 3proxy to start existing container
send this to standard input (example):
nserver 8.8.8.8
nscache 65535
log
proxy -p3129
end
nserver is required for DNS resolutions.
Some proxy types (e.g. SOCKSv5 UDPASSCOC, SOCKSv5 BIND functionality, ftp proxy) require access to ephemeral port, you may use e.g. --network host mode or -P to docker run.
:minimal without version specified uses current stable version.
Building and installation
Windows Installation
Install and start proxy as Windows service:
bash
3proxy [path_to_config_file] --install
Config file should be Top issues
#740Source in ACL names does not work20 comments · 2022-02-09#63handle authentication with external script17 comments · 2016-04-21#649Prometheus metrics10 comments · 2021-06-07#21ICAP support4 comments · 2015-10-25#747Problem in Radius Accounting ( log radius )3 comments · 2022-02-27#1272Прокси http, https и socks5 на одном порту2 comments · 2026-09-04#665Need bandwidth limiter work with source port2 comments · 2021-07-27#1190How to add users to the Windows application 3proxy using the /etc/3proxy/conf/add3proxyuser.sh script, similar to Linux.1 comments · 2026-02-10
Discussions
#1223Commit #ec48b7f30e3ffb864b1286f19cec4f7d3b13fb8f: Unable to fully compile 3proxy repo package in Linux1 comments · 2026-05-07#1221Commit #830b2d39d138bfa0789543e7d8df04fd09437473: UDP in 3proxy and 3proxy_socks doesn't work.6 comments · 2026-05-04#1219Latest 3proxy (commit da8a8615f476bbe3b84b128356612ab08e411201) fails to start and return a "Segmentation fault" when "-l" option is passed to cmd line2 comments · 2026-05-03#1217Вопросы, комментарии, багрепорты и запросы фич #107 comments · 2026-04-27#1216Questions, comments, bugreports and feature requests #45 comments · 2026-04-27
Latest release
3proxy-1.0.3 1.0.3 2026-11-07Security fixes (RADIUS, reverse DNS authentication), stability and performance fixes, -s renamed to -B for SNI break ! Fix: RADIUS authentication: the reply digest copied the shared secret right after the received bytes, so a reply of 4100 bytes with a secret of 17 or more characters wrote up to 47 bytes of it past the reply buffer on the stack, before the reply was authenticated; the digest is hashed over the reply and the secret in place now, with nothing written past the reply, and a reply is taken only from the address and port of the server the request went to, with the request's ident