Docker container for managing Nginx proxy hosts with a simple, powerful interface https://nginxproxymanager.com
Find a file
Tom Winnerl b7720afab4 fix(review): don't block saving because of a disabled location's host
Problem: validateLocations() ran the host format checks (whitespace,
characters such as ; $ { }, invalid characters in the host/path part) on
every non-blank row, also on rows switched off with `enabled: false`. The
backend never renders a disabled location (preflightLocation() stops at
`enabled: false`) and the API accepts such a host, so a stored location with
an invalid host could be disabled safely, yet the editor refused to save
the host until the disabled row was fixed or deleted.

Fix: a disabled row only gets the checks the API itself makes for every
row: required path and host, the port range, and duplicate paths (the
backend's findDuplicatePath() counts disabled rows too). Switching the row
back on brings the format errors back, because validation runs on every
change.

Tests: validateLocations cases for disabled rows (format errors skipped,
required / port / duplicate checks kept, the same rows enabled still
invalid) and a form test: a disabled row with a stored `app;legacy` host
submits, after switching it on the submit is blocked again.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-14 09:03:56 +01:00
.github Update pull request template 2026-11-05 10:34:33 +10:00
backend fix(review): quarantine a location behind an error without a line 2026-11-14 09:03:56 +01:00
docker fix(review): keep real errors about /var/log/nginx/error.log in the startup check too 2026-11-13 19:23:04 +01:00
docs fix(review): quarantine a location behind an error without a line 2026-11-14 09:03:56 +01:00
frontend fix(review): don't block saving because of a disabled location's host 2026-11-14 09:03:56 +01:00
scripts Stop non-admins injecting nginx directives through host fields 2026-11-10 08:20:02 +10:00
test fix(review): quarantine a location behind an error without a line 2026-11-14 09:03:56 +01:00
.gitattributes Add .gitattributes to keep LF line endings 2026-11-02 20:28:33 -08:00
.gitignore Fix for changing the upstream Host from $host to $forward_host 2026-11-09 22:09:34 +10:00
.version Bump mid version, as Tabler has changed the dark UI it's worth more than a revision change 2026-11-05 08:38:55 +10:00
LICENSE Initial commit 2017-12-21 09:01:17 +10:00
README.md Bump mid version, as Tabler has changed the dark UI it's worth more than a revision change 2026-11-05 08:38:55 +10:00
SECURITY.md Bump version 2026-09-23 14:10:29 +10:00



This project comes as a pre-built Docker image that enables you to easily forward to your websites running at home or otherwise, including free SSL, without having to know too much about Nginx or Letsencrypt.

Project Goal

I created this project to fill a personal need to provide users with an easy way to accomplish reverse proxying hosts with SSL termination, and it had to be so easy that a monkey could do it. This goal hasn't changed. While there might be advanced options, they are optional, and the project should be as simple as possible so that the barrier to entry here is low.

Buy Me A Coffee

Features

  • Beautiful and Secure Admin Interface based on Tabler
  • Easily create forwarding domains, redirections, streams, and 404 hosts without knowing anything about Nginx
  • Free SSL using Let's Encrypt or provide your own custom SSL certificates
  • Access Lists and basic HTTP Authentication for your hosts
  • Advanced Nginx configuration available for super users
  • User management, permissions, and audit log

::: warning armv7 is no longer supported in version 2.14+. This is due to Nodejs dropping support for armhf. Please use the 2.13.7 image tag if this applies to you. :::

Hosting your home network

I won't go into too much detail here, but here are the basics for someone new to this self-hosted world.

  1. Your home router will have a Port Forwarding section somewhere. Log in and find it
  2. Add port forwarding for ports 80 and 443 to the server hosting this project
  3. Configure your domain name details to point to your home, either with a static ip or a service like
  4. Use the Nginx Proxy Manager as your gateway to forward to your other web-based services

Quick Setup

  1. Install Docker
  2. Create a docker-compose.yml file similar to this:
services:
  app:
    image: 'docker.io/jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

This is the bare minimum configuration required. See the documentation for more.

  1. Bring up your stack by running
docker compose up -d
  1. Log in to the Admin UI

When your docker container is running, connect to it on port 81 for the admin interface. Sometimes this can take a little bit because of the entropy of keys.

http://127.0.0.1:81

Contributing

All are welcome to create pull requests for this project, against the develop branch. Official releases are created from the master branch.

CI is used in this project. All PR's must pass before being considered. After passing, docker builds for PR's are available on dockerhub for manual verifications.

Documentation within the develop branch is available for preview at https://develop.nginxproxymanager.com

Contributors

Special thanks to all of our contributors.

Getting Support

  1. Found a bug?
  2. Discussions
  3. Reddit