Original Summary

I've run into the same problem more than once: a team needs a proxy with users and limits. Envoy or Squid can do it, but someone has to set them up, run them and handle every change, and DevOps usually have better things to do. I looked for a self-hosted proxy with a normal admin panel and didn't find one I liked. So in my spare time I started writing my own. It's called Proxium: an HTTP and SOCKS5 proxy where users, limits and outgoing IPs are stored in a database and managed in the browser. Changes apply in a few seconds, no restart. What works now: username/password or token per user, with expiry speed limits and traffic quotas per day or month rules like "1 Mbit/s during work hours, except GitHub" outgoing IP from a pool, or a dedicated one per user admins with separate permissions, e.g. support can revoke users but can't touch certificates local network and cloud metadata are blocked by default Stack: Python (asyncio proxy, FastAPI for the API), PostgreSQL, React admin. All in one Docker image, amd64 and arm64: docker run -d --name proxium \ -p 80:80 -p 8080:8080 \ -v proxium:/var/lib/proxium \ -e SUPERUSER_CREATE=true \ -e SUPERUSER_EMAIL=admin@example.com \ -e SUPERUSER_PASSWORD=change-me \ ikoldakov/proxium Admin is at http://localhost , proxy on port 8080. For a real server, HTTPS for the admin is one env var: Let's Encrypt, your own ACME server, your own certificate files, or self-signed for networks without internet. Proxy TLS certificates are uploaded in the admin, generated self-signed or imported from certbot. The code is MIT: use it at work, change it, fork it, sell it, just keep the license notice. Docs: https://proxium.koldakov.com Code: https://github.com/koldakov/proxium If your team uses a proxy, how do you manage users and limits today? Trying to figure out who else has this problem.   submitted by   /u/koldakov [link]   [comments]

  • 情报分类：服务器与云资源
  • 分类依据：内容涉及服务器、云资源或网络线路
  • 信息来源：Reddit · SideProject
  • 发布时间：2026/10/11 23:41:12