lets-proxy2
A reverse proxy that automatically obtains and renews TLS certificates from Let's Encrypt with zero configuration.
What is lets-proxy2?
Lets-proxy2 is a reverse proxy server that automatically obtains and manages TLS certificates from Let's Encrypt to transparently handle HTTPS requests. It simplifies HTTPS setup by eliminating manual certificate management, listening on port 443 and proxying requests to port 80 while adding headers like X-Forwarded-For. It is designed to work with minimal configuration, making secure HTTPS proxying accessible for various server environments.
System administrators and developers managing shared hosting environments with many domains, as well as individuals running personal servers or VPS instances who need automated HTTPS. It is suitable for those seeking a zero-config solution for TLS certificate management.
Developers choose Lets-proxy2 for its automatic, zero-configuration TLS certificate handling from Let's Encrypt, which removes the complexity of manual certificate setup and renewal. Its unique selling point is the ability to handle thousands of domains per server efficiently, with built-in security controls like domain blacklisting/whitelisting and pre-issue checks to prevent abuse.
Overview
Reverse proxy with automatically obtains TLS certificates from Let's Encrypt
Use Cases
Best For
- Setting up HTTPS on a personal server or VPS without manual certificate configuration.
- Managing TLS certificates for shared hosting environments with many thousands of domains.
- Automating Let's Encrypt certificate issuance and renewal for reverse proxy scenarios.
- Implementing IP-based backend routing for incoming HTTPS connections.
- Adding Prometheus metrics monitoring to a reverse proxy setup.
- Enforcing security policies with domain blacklisting/whitelisting and certificate locking.
Not Ideal For
- Environments requiring advanced reverse proxy features like caching, load balancing algorithms, or WebSocket support.
- Internal networks or intranets where public domain validation via Let's Encrypt is not possible.
- Projects needing integration with certificate authorities other than Let's Encrypt.
Pros & Cons
Pros
Automatically obtains and renews TLS certificates from Let's Encrypt using SNI from requests, eliminating manual certificate setup and renewal, as highlighted in the README's zero-config philosophy.
Works out of the box with no initial configuration, making it easy to deploy for quick HTTPS setup on personal servers or VPS, as demonstrated by the simple './lets-proxy' command.
Designed to handle thousands of domains per server with features like domain blacklisting/whitelisting and pre-issue checks, ensuring robustness in high-volume hosting scenarios.
Supports logging to stderr and files with self-rotation, and offers optional Prometheus metrics for monitoring, providing detailed insights into proxy performance.
Cons
Focuses primarily on HTTPS proxying and certificate management, lacking built-in capabilities like caching, URL rewriting, or advanced load balancing that are common in more comprehensive proxies like Nginx.
Tied exclusively to Let's Encrypt for certificates, so API changes or downtime could disrupt service, and it doesn't natively support other certificate authorities, limiting flexibility.
Issues certificates on-demand via SNI, which may cause delays for initial requests to new domains while obtaining certificates from Let's Encrypt, impacting user experience in dynamic environments.
Frequently Asked Questions
Related Projects
CaddyFast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
minioMinIO is a high-performance, S3 compatible object store, open sourced under GNU AGPLv3 license.
etcdDistributed reliable key-value store for the most critical data of a distributed system
SFTPGoFull-featured and highly configurable SFTP, HTTP/S, FTP/S and WebDAV server - S3, Google Cloud Storage, Azure Blob
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.