Portainer Templates logo

Portainer Templates

Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE

Container

ProxyTools

DEVEL Not ready for production. Nginx Proxy Manager v3 Develop 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. Please see the install document at https://github.com/pi-hosted/pi-hosted/tree/master/docs installing the template

Image details

Pulls: 267.3M
Architecture: amd64, arm64, arm/v7
Image size: 432 MB
Latest: 2.15.1
User: jc21
Created: Dec 11, 2017
Updated: 2 months ago
Status: active

Source details

Repo: jc21/nginx-proxy-manager
Stars: 33.9k
Forks: 4k
Language: TypeScript
License: MIT
Latest: v2.15.1 · 2 months ago
Updated: 4 days ago
Website: nginxproxymanager.com/

Configuration

Type
Container
Platform
linux
Image
jc21/nginx-proxy-manager:v3
Ports
80:80/tcp81:81/tcp443:443/tcp
Volumes
/data : /portainer/Files/AppData/Config/nginx-proxy-manager-v3/data
Env vars
PUID=1000PGID=1000TZ=America/New_York
Restart
unless-stopped

Template by novaspirit

Notes

Template created by Pi-Hosted Series
Check our Github page: https://github.com/pi-hosted/pi-hosted

Official Webpage: https://nginxproxymanager.com/
Official Docker Documentation: https://nginxproxymanager.com/setup/

Pi-Hosted dedicated documentation: nginx_proxy_manager.md




Youtube Video: Novaspirit Tech - Installing Nginx Proxy Manager on Docker

Standalone Install

Select an install method, to see config/commands for deploying Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo

More install options in our documentation, or see jc21/nginx-proxy-manager for app-specific guidance.

<img src="https://nginxproxymanager.com/github.png">
<br><br>
<a href="https://hub.docker.com/repository/docker/jc21/nginx-proxy-manager">
	<img src="https://img.shields.io/docker/stars/jc21/nginx-proxy-manager.svg?style=for-the-badge">
</a>
<a href="https://hub.docker.com/repository/docker/jc21/nginx-proxy-manager">
	<img src="https://img.shields.io/docker/pulls/jc21/nginx-proxy-manager.svg?style=for-the-badge">
</a>


The official repo of Nginx Proxy Manager.

Serve Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying nginx-proxy-manager-v3-devel-not-ready-for-use.example.com to http://nginx-proxy-manager-v3:80

Add this to your Caddyfile

nginx-proxy-manager-v3-devel-not-ready-for-use.example.com {
	reverse_proxy http://nginx-proxy-manager-v3:80
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs nginx-proxy-manager-v3
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:80 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :80
  • Stop the other service, or pick a different host port. In 80:80 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:80. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, nginx-proxy-manager-v3 can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 80

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/nginx-proxy-manager-v3/data
  • Or set the PUID and PGID variables (defaults 1000:1000) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull jc21/nginx-proxy-manager:v3

  • "manifest unknown" means the tag no longer exists.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64, arm/v7
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

  • Check the logs right after a restart, the last few lines before it died are the useful ones.
  • Get the exit code with docker inspect nginx-proxy-manager-v3 --format '{{.State.ExitCode}}'
  • Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A single container

Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.

The app image

An image is the app packed up ready to go, everything Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE needs bundled into one download. This template pulls jc21/nginx-proxy-manager:v3, which Docker fetches once (about 432 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE's comes from Docker Hub, published by jc21.

Version tags

The bit after the colon in the image name is the version tag. This one pins v3, so every redeploy gives you that exact build until you bump it yourself.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, arm/v7, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 80:80 means it's reachable on port 80 of your server, where the left number is yours to change and the right one belongs to the app. Once it's running, open http://your-server-ip:80 in a browser. It opens:

  • 80:80, likely the web interface
  • 81:81
  • 443:443, likely the web interface

Volumes

A volume is where Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /data from /portainer/Files/AppData/Config/nginx-proxy-manager-v3/data on the host

Environment variables

Environment variables are the settings you hand over when you deploy, things like a password or a timezone. Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE takes 3 of them, all with defaults you can leave alone or tweak:

  • PUID, defaults to 1000
  • PGID, defaults to 1000
  • TZ, defaults to America/New_York

Restart policy

The restart policy here is unless-stopped, so Docker restarts Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE after a crash or reboot, but leaves it off when you stop it on purpose. You can change this on the deploy screen. The choices are no (never restart), on-failure (only after a crash), unless-stopped (restart unless you stop it), and always (bring it back no matter what).

Users and permissions

The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.

Networking

Nothing custom is set, so Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container nginx-proxy-manager-v3. That's what you'll spot in the containers list and use in commands like docker logs nginx-proxy-manager-v3.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Open source license

Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE is open source, released under the MIT license. In plain terms the code is out in the open, so you're free to run it and change it to fit what you need.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE up. Add the template list to Portainer once, then deploying Nginx Proxy Manager v3 [DEVEL] NOT READY FOR USE is a click rather than a wall of config.