SNIProxy
SNI Proxy is a lightweight TCP-layer proxy that inspects the Server Name Indication (SNI) hostname in each incoming HTTPS connection and forwards it to the…
Platform availability
Available on 1 of 10 platforms
- Unraid
- TrueNAS (not listed)
- Umbrel (not listed)
- ZimaOS (not listed)
- Proxmox (not listed)
- Helm (not listed)
- Mac (not listed)
- Windows (not listed)
- Linux (not listed)
- Any server (not listed)
Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.
62/100 Good
- Maintained
- 72last commit 28 days ago
- Popular
- 692,721 GitHub stars
- Easy to install
- 351 install platform, install notes, Docker image
- Light to run
- No data
- Security check
- 59no serious findings, tests, OpenSSF Scorecard 2/10
Based on 4 of 5 factors.
Availability: platform listings confirmed today, links checked 52 days ago
- GitHub stars
- 2,721
- Open issues
- 122
- Last commit
- 2026-10-24
- License
- BSD-2-Clause
- Activity
- rising
Checked 20 days ago - source: GitHub (dlundquist/sniproxy)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is not supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Use the install script Run the provided bash installer to install sniproxy and create its systemd service. This avoids missing manual steps and helps the app start automatically. source
- Configure the listening port In the YAML config, set bind_https to the port you want clients to connect to, such as 0.0.0.0:443. If this is wrong, your devices will not be able to reach the proxy. source
- Set DNS and traffic rules Also fill in upstream DNS (the DNS server that resolves domain names) and ACL (allow/block rules) in the config. Without correct values, name lookups or routing can fail. source
- Install instructions Follow the project's official install instructions (the article at squishedmooo.com/?p=1); the author notes they are required for a working setup. source
Fetched 46 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
Why might SNIProxy fail to route HTTP/2 or HTTP/3 traffic correctly?
It does not support those protocols, and HTTP/2 can multiplex multiple hostnames in one TCP stream while HTTP/3 uses UDP transport.
Where does SNIProxy look for its configuration file by default?
It defaults to /etc/sniproxy.conf, and a different file can be specified with the -c flag.
How can backend servers learn the original client address?
Use the HAProxy proxy protocol, which SNIProxy supports to propagate the original source address to back-end servers.
Can one SNIProxy instance use multiple listeners?
Yes, it supports multiple listening sockets per instance.
Answers sourced from github.com
Community
- Avoid SNI snooping without VPN : r/selfhosted - Reddit (reddit)
- Forward SNI proxy with multiple gateways : r/selfhosted - Reddit (reddit)
- Made a small and simple self-hosted SmartDNS Proxy : r/selfhosted - Reddit (reddit)
Collected 53 days ago - public community threads