steveltn/https-portal

A fully automated HTTPS server powered by Nginx, Let's Encrypt and Docker.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 8 minutes ago
Added to GitGenius on September 14th, 2026
Created on December 14th, 2015
Open Issues & Pull Requests: 52 (+0)
GitHub issues: Enabled
Number of forks: 296
Total Stargazers: 4,694 (+0)
Total Subscribers: 87 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 2.2 days
Mean response time: 19.8 days
90th percentile: 63.1 days
Tracked items: 15

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 9
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 508 days
Stale 30+ days: 8
Stale 90+ days: 8

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

HTTPS-PORTAL is a Docker container that automates HTTPS deployment by combining Nginx, Let's Encrypt, and Docker into a single managed service.

The tool solves the problem of setting up and maintaining HTTPS infrastructure for web applications. It automatically obtains SSL certificates from Let's Encrypt and handles their renewal without manual intervention. The approach works by running as a Docker container that acts as a reverse proxy, intercepting traffic on ports 80 and 443 and routing it to your application while managing all certificate lifecycle operations transparently.

HTTPS-PORTAL suits teams running applications in Docker environments who want HTTPS without operational overhead. It works with existing web applications by adding a single configuration layer, requiring only that you have a Linux machine with Docker, available ports 80 and 443, and domains resolving to that machine. The tool supports multiple domains, custom ports, multiple upstream servers, static site serving, HTTP basic authentication, and access restrictions. It can also work in hybrid setups with non-dockerized applications and allows sharing certificates across multiple apps. Advanced users can configure Nginx through environment variables, override configuration files, or adjust private key parameters.

The project shows consistent maintenance with regular updates addressing user-reported issues and feature requests. Development activity includes responsiveness to bug reports and incorporation of community feedback into releases. The maintainers provide comprehensive documentation covering common use cases and troubleshooting scenarios, though some documentation like the Japanese README may lag behind the primary English version.