New: the Homelab Planning Bundle. Both planners together for $19.99 instead of $27.98Save $7.99GET THE BUNDLE

Homelab Addiction

Self-Hosted / Projects / Nginx Proxy Manager

Nginx Proxy Manager

Stable
NginxProxyManager/nginx-proxy-manager34.4k3.9k2d agoWeb Servers

Specs verified August 25, 2026 · against v2.15.1

Overview

Self-hosted reverse proxy manager with a GUI, Let's Encrypt, and access controls.

Nginx Proxy Manager is a self-hosted reverse proxy manager for people who want to publish homelab web services behind one gateway without writing raw Nginx config for every host.

Why people choose Nginx Proxy Manager

The official site frames it as an easy and secure way to expose services, with built-in Let's Encrypt support and a UI for proxy hosts, redirects, streams, and access controls. That makes it attractive for beginners who find Caddy labels or hand-written Nginx files intimidating.

What is included

Official docs cover proxy hosts, redirection hosts, streams, 404 hosts, access lists, basic authentication, custom certificates, audit logs, multi-user access, and optional advanced configuration snippets for power users.

What to know before you deploy

Nginx Proxy Manager makes reverse proxying easier, but it does not remove the security work. You still need correct DNS, port forwarding, backups, and sensible exposure decisions. The project is also packaged around Docker, so it is best for users already comfortable with container-based deployment.

Best fit

Choose Nginx Proxy Manager when you want a GUI-driven reverse proxy for a small homelab or team. If you want infrastructure-as-code automation first, label-driven proxies or native Nginx configuration may fit better.

Interface previews

Screenshots of the Nginx Proxy Manager interface.

Feature support

Feature support in Nginx Proxy Manager
FeatureSupport
Proxy hosts and redirectsOfficial docs say it can create forwarding domains, redirections, streams, and 404 hosts from the web UI.Supported
Free Let's Encrypt certificatesThe project homepage and guide highlight built-in Let's Encrypt support with auto-renewal.Supported
Custom SSL certificatesOfficial setup and feature docs say you can provide your own certificates.Supported
Access lists and basic authOfficial docs explicitly list access lists and HTTP authentication.Supported
Streams and non-HTTP forwardingThe UI supports stream entries as well as standard web proxy hosts.Supported
Advanced Nginx snippetsAdvanced configuration is available, but it is aimed at more experienced users.Partial support
Multi-user permissions and audit logOfficial feature lists include user management, permissions, and audit logging.Supported
Multiple database backendsOfficial setup docs document SQLite, MariaDB/MySQL, and PostgreSQL options.Supported

Community signals

Stars
34.4k
Forks
3.9k
Open issues
867

Includes open pull requests

Last commit
2d ago
Latest release
v2.16.0

2w ago

Repo created
Dec 2017

Refreshed nightly from the GitHub API.

Questions

What is Nginx Proxy Manager used for?

Nginx Proxy Manager is used to publish self-hosted web services behind one reverse proxy using a browser-based admin interface instead of manual Nginx config.

Does Nginx Proxy Manager support Let's Encrypt?

Yes. The official site says it includes built-in Let's Encrypt support and can also use custom SSL certificates.

Do you have to use Docker for Nginx Proxy Manager?

Yes. The official FAQ says Docker is how the project is packaged and supported.

What ports does Nginx Proxy Manager use?

The official setup docs use port 80 for HTTP, 443 for HTTPS, and 81 for the admin interface.

Can Nginx Proxy Manager run on Raspberry Pi?

Yes. The official FAQ says the image is multi-architecture, but the docs note that armv7 is no longer supported from version 2.14 onward.

Can Nginx Proxy Manager use SQLite, MariaDB, or PostgreSQL?

Yes. Official setup docs cover the default SQLite path plus MariaDB/MySQL and PostgreSQL configurations.

Is Nginx Proxy Manager the same as exposing services safely by default?

No. It simplifies proxy setup, but you still need to handle DNS, port forwarding, updates, and the security consequences of exposing services to the internet.

support // the lab

Found this write-up useful?

If it saved you time or a rebuild, you can support more practical homelab guides.

Support the lab