[{"_1":2,"_155":-5,"_156":-5},"loaderData",{"_3":4,"_13":14,"_21":22,"_134":135},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","routes/_layout",{"_15":-5,"_16":17,"_18":17,"_19":11,"_20":11},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_23":24,"_25":-5,"_26":11,"_27":11,"_28":29,"_30":31,"_32":-5,"_33":11,"_34":35,"_84":-5,"_85":86,"_125":-5,"_126":11,"_127":17,"_128":11,"_129":-5,"_130":11,"_131":-5,"_132":133},"canonicalUrl","https://hub.docker.com/r/neebs42/nginx-proxy-manager/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","neebs42","reponame","nginx-proxy-manager","cloudBuildSource","isAutobuildsAvailable","repo",{"_36":37,"_38":39,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":51,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":70,"_75":11,"_76":77,"_81":29,"_82":83},"categories",[],"content_types",[40],"image","date_registered","2019-05-29T22:59:25.067954Z","description","clone of https://hub.docker.com/r/jlesage/nginx-proxy-manager/ but using 80,443 docker & VLAN","is_private","last_updated","2019-05-31T10:17:10.031639Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[52],"application/vnd.docker.container.image.v1+json","name","pull_count",23133,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","# Docker container for Nginx Proxy Manager\n[![Docker Automated build](https://img.shields.io/docker/automated/jlesage/nginx-proxy-manager.svg)](https://hub.docker.com/r/jlesage/nginx-proxy-manager/) [![Docker Image](https://images.microbadger.com/badges/image/jlesage/nginx-proxy-manager.svg)](http://microbadger.com/#/images/jlesage/nginx-proxy-manager) [![Build Status](https://travis-ci.org/jlesage/docker-nginx-proxy-manager.svg?branch=master)](https://travis-ci.org/jlesage/docker-nginx-proxy-manager) [![GitHub Release](https://img.shields.io/github/release/jlesage/docker-nginx-proxy-manager.svg)](https://github.com/jlesage/docker-nginx-proxy-manager/releases/latest) [![Donate](https://img.shields.io/badge/Donate-PayPal-green.svg)](https://paypal.me/JocelynLeSage/0usd)\n\nThis is a Docker container for Nginx Proxy Manager.\n\n---\n\n[![Nginx Proxy Manager logo](https://images.weserv.nl/?url=raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/nginx-proxy-manager-icon.png&w=200)](https://nginxproxymanager.jc21.com)[![Nginx Proxy Manager](https://dummyimage.com/400x110/ffffff/575757&text=Nginx+Proxy+Manager)](https://nginxproxymanager.jc21.com)\n\nNginx Proxy Manager 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.\n\n---\n\n## Table of Content\n\n * [Docker container for Nginx Proxy Manager](#docker-container-for-nginx-proxy-manager)\n * [Table of Content](#table-of-content)\n * [Quick Start](#quick-start)\n * [Usage](#usage)\n * [Environment Variables](#environment-variables)\n * [Data Volumes](#data-volumes)\n * [Ports](#ports)\n * [Changing Parameters of a Running Container](#changing-parameters-of-a-running-container)\n * [Docker Compose File](#docker-compose-file)\n * [Docker Image Update](#docker-image-update)\n * [Synology](#synology)\n * [unRAID](#unraid)\n * [User/Group IDs](#usergroup-ids)\n * [Accessing the GUI](#accessing-the-gui)\n * [Shell Access](#shell-access)\n * [Default Administrator Account](#default-administrator-account)\n * [Accessibility From The Internet](#accessibility-from-the-internet)\n * [Support or Contact](#support-or-contact)\n\n## Quick Start\n\n**NOTE**: The Docker command provided in this quick start is given as an example\nand parameters should be adjusted to your need.\n\nLaunch the Nginx Proxy Manager docker container with the following command:\n```\ndocker run -d \\\n --name=nginx-proxy-manager \\\n -p 8181:8181 \\\n -p 8080:8080 \\\n -p 4443:4443 \\\n -v /docker/appdata/nginx-proxy-manager:/config:rw \\\n jlesage/nginx-proxy-manager\n```\n\nWhere:\n - `/docker/appdata/nginx-proxy-manager`: This is where the application stores its configuration, log and any files needing persistency.\n\nBrowse to `http://your-host-ip:8181` to access the Nginx Proxy Manager web interface.\n\n## Usage\n\n```\ndocker run [-d] \\\n --name=nginx-proxy-manager \\\n [-e =]... \\\n [-v :[:PERMISSIONS]]... \\\n [-p :]... \\\n jlesage/nginx-proxy-manager\n```\n| Parameter | Description |\n|-----------|-------------|\n| -d | Run the container in background. If not set, the container runs in foreground. |\n| -e | Pass an environment variable to the container. See the [Environment Variables](#environment-variables) section for more details. |\n| -v | Set a volume mapping (allows to share a folder/file between the host and the container). See the [Data Volumes](#data-volumes) section for more details. |\n| -p | Set a network port mapping (exposes an internal container port to the host). See the [Ports](#ports) section for more details. |\n\n### Environment Variables\n\nTo customize some properties of the container, the following environment\nvariables can be passed via the `-e` parameter (one for each variable). Value\nof this parameter has the format `=`.\n\n| Variable | Description | Default |\n|----------------|----------------------------------------------|---------|\n|`USER_ID`| ID of the user the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n|`GROUP_ID`| ID of the group the application runs as. See [User/Group IDs](#usergroup-ids) to better understand when this should be set. | `1000` |\n|`SUP_GROUP_IDS`| Comma-separated list of supplementary group IDs of the application. | (unset) |\n|`UMASK`| Mask that controls how file permissions are set for newly created files. The value of the mask is in octal notation. By default, this variable is not set and the default umask of `022` is used, meaning that newly created files are readable by everyone, but only writable by the owner. See the following online umask calculator: http://wintelguy.com/umask-calc.pl | (unset) |\n|`TZ`| [TimeZone] of the container. Timezone can also be set by mapping `/etc/localtime` between the host and the container. | `Etc/UTC` |\n|`KEEP_APP_RUNNING`| When set to `1`, the application will be automatically restarted if it crashes or if user quits it. | `0` |\n|`APP_NICENESS`| Priority at which the application should run. A niceness value of -20 is the highest priority and 19 is the lowest priority. By default, niceness is not set, meaning that the default niceness of 0 is used. **NOTE**: A negative niceness (priority increase) requires additional permissions. In this case, the container should be run with the docker option `--cap-add=SYS_NICE`. | (unset) |\n|`CLEAN_TMP_DIR`| When set to `1`, all files in the `/tmp` directory are delete during the container startup. | `1` |\n\n### Data Volumes\n\nThe following table describes data volumes used by the container. The mappings\nare set via the `-v` parameter. Each mapping is specified with the following\nformat: `:[:PERMISSIONS]`.\n\n| Container path | Permissions | Description |\n|-----------------|-------------|-------------|\n|`/config`| rw | This is where the application stores its configuration, log and any files needing persistency. |\n\n### Ports\n\nHere is the list of ports used by the container. They can be mapped to the host\nvia the `-p` parameter (one per port mapping). Each mapping is defined in the\nfollowing format: `:`. The port number inside the\ncontainer cannot be changed, but you are free to use any port on the host side.\n\n| Port | Mapping to host | Description |\n|------|-----------------|-------------|\n| 8181 | Mandatory | Port used to access the web interface of the application. |\n| 8080 | Mandatory | Port used to serve HTTP requests. |\n| 4443 | Mandatory | Port used to serve HTTPs requests. |\n\n### Changing Parameters of a Running Container\n\nAs seen, environment variables, volume mappings and port mappings are specified\nwhile creating the container.\n\nThe following steps describe the method used to add, remove or update\nparameter(s) of an existing container. The generic idea is to destroy and\nre-create the container:\n\n 1. Stop the container (if it is running):\n```\ndocker stop nginx-proxy-manager\n```\n 2. Remove the container:\n```\ndocker rm nginx-proxy-manager\n```\n 3. Create/start the container using the `docker run` command, by adjusting\n parameters as needed.\n\n**NOTE**: Since all application's data is saved under the `/config` container\nfolder, destroying and re-creating a container is not a problem: nothing is lost\nand the application comes back with the same state (as long as the mapping of\nthe `/config` folder remains the same).\n\n## Docker Compose File\n\nHere is an example of a `docker-compose.yml` file that can be used with\n[Docker Compose](https://docs.docker.com/compose/overview/).\n\nMake sure to adjust according to your needs. Note that only mandatory network\nports are part of the example.\n\n```yaml\nversion: '3'\nservices:\n nginx-proxy-manager:\n build: .\n ports:\n - \"8181:8181\"\n - \"8080:8080\"\n - \"4443:4443\"\n volumes:\n - \"/docker/appdata/nginx-proxy-manager:/config:rw\"\n```\n\n## Docker Image Update\n\nIf the system on which the container runs doesn't provide a way to easily update\nthe Docker image, the following steps can be followed:\n\n 1. Fetch the latest image:\n```\ndocker pull jlesage/nginx-proxy-manager\n```\n 2. Stop the container:\n```\ndocker stop nginx-proxy-manager\n```\n 3. Remove the container:\n```\ndocker rm nginx-proxy-manager\n```\n 4. Start the container using the `docker run` command.\n\n### Synology\n\nFor owners of a Synology NAS, the following steps can be use to update a\ncontainer image.\n\n 1. Open the *Docker* application.\n 2. Click on *Registry* in the left pane.\n 3. In the search bar, type the name of the container (`jlesage/nginx-proxy-manager`).\n 4. Select the image, click *Download* and then choose the `latest` tag.\n 5. Wait for the download to complete. A notification will appear once done.\n 6. Click on *Container* in the left pane.\n 7. Select your Nginx Proxy Manager container.\n 8. Stop it by clicking *Action*->*Stop*.\n 9. Clear the container by clicking *Action*->*Clear*. This removes the\n container while keeping its configuration.\n 10. Start the container again by clicking *Action*->*Start*. **NOTE**: The\n container may temporarily disappear from the list while it is re-created.\n\n### unRAID\n\nFor unRAID, a container image can be updated by following these steps:\n\n 1. Select the *Docker* tab.\n 2. Click the *Check for Updates* button at the bottom of the page.\n 3. Click the *update ready* link of the container to be updated.\n\n## User/Group IDs\n\nWhen using data volumes (`-v` flags), permissions issues can occur between the\nhost and the container. For example, the user within the container may not\nexists on the host. This could prevent the host from properly accessing files\nand folders on the shared volume.\n\nTo avoid any problem, you can specify the user the application should run as.\n\nThis is done by passing the user ID and group ID to the container via the\n`USER_ID` and `GROUP_ID` environment variables.\n\nTo find the right IDs to use, issue the following command on the host, with the\nuser owning the data volume on the host:\n\n id \n\nWhich gives an output like this one:\n```\nuid=1000(myuser) gid=1000(myuser) groups=1000(myuser),4(adm),24(cdrom),27(sudo),46(plugdev),113(lpadmin)\n```\n\nThe value of `uid` (user ID) and `gid` (group ID) are the ones that you should\nbe given the container.\n\n## Accessing the GUI\n\nAssuming that container's ports are mapped to the same host's ports, the\ninterface of the application can be accessed with a web browser at:\n\n```\nhttp://:8181\n```\n\n## Shell Access\n\nTo get shell access to a the running container, execute the following command:\n\n```\ndocker exec -ti CONTAINER sh\n```\n\nWhere `CONTAINER` is the ID or the name of the container used during its\ncreation (e.g. `crashplan-pro`).\n\n## Default Administrator Account\n\nAfter a fresh install, use the following credentials to login:\n - Email address: `admin@example.com`\n - Password: `changeme`\n\nAfter you login with this default user, you will be asked to modify your details\nand change your password.\n\n## Accessibility From The Internet\n\n**NOTE:** This section assumes that the container is using the default `bridge`\nnetwork type.\n\nFor this container to be accessible from the Internet, port forwarding must be\nconfigured on your router. This allows HTTP (port 80) and HTTPs (port 443)\ntraffic from the Internet to reach this container on your private network.\n\nConfiguration of port forwarding differs from one router to another, but in\ngeneral the same information must be configured:\n - **External port**: The Internet-side port to be forwarded.\n - **Internal port**: The port to forward to. Also called private port.\n - **Destination IP address**: The IP address of the device on the local\n network to forward to. Also called private IP address.\n\nThe IP address to forward to should be the IP address of the host running the\ncontainer. The port to forward to should be the port mapped to the container\nduring its creation (via the `-p` parameter of the `docker run` command).\n\nSince the container needs to handle both HTTP and HTTPs traffic, two ports need\nto be forwarded:\n\n| Traffic type | Container port | Host port mapped to container | External port | Internal port | Internal IP address |\n|--------------|----------------|-------------------------------|---------------|---------------|-----------------------------------------------|\n| HTTP | 8080 | XXXX | 80 | XXXX | IP address of the host running the container. |\n| HTTPs | 4443 | YYYY | 443 | YYYY | IP address of the host running the container. |\n\n`XXXX` and `YYYY` are configurable port values. Unless they conflict with other\nused ports on the host, they can simply be set to the same value as the\ncontainer port.\n\n**NOTE**: Some routers don't offer the ability to configure the internal port\nto forward to. This means that internal port is the same as the external one.\nIn a such scenario, `XXXX` must be set to `80` and `YYYY` to `443`.\n\nFor more details about port forwarding, see the following links:\n - [How to Port Forward - General Guide to Multiple Router Brands](https://www.noip.com/support/knowledgebase/general-port-forwarding-guide/)\n - [How to Forward Ports on Your Router](https://www.howtogeek.com/66214/how-to-forward-ports-on-your-router/)\n\n[TimeZone]: http://en.wikipedia.org/wiki/List_of_tz_database_time_zones\n\n## Support or Contact\n\nHaving troubles with the container or have questions? Please\n[create a new issue].\n\nFor other great Dockerized applications, see https://jlesage.github.io/docker-apps.\n\n[create a new issue]: https://github.com/jlesage/docker-nginx-proxy-manager/issues\n","has_starred","hub_user","immutable_tags_settings",{"_71":11,"_72":73},"enabled","rules",[74],".*","is_automated","permissions",{"_78":17,"_79":11,"_80":11},"read","write","admin","user","storage_size",376666051,"orgData","recentTags",[87],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":96,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},"content_type","creator",3232408,"full_size",96113572,"id",57419595,"images",[97],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},"architecture","amd64","digest","sha256:accaea7c7f5a2693a2336e96ad3d82e72b49891be0d433ada87a7835c19038ed","features","","last_pulled","2026-09-25T07:15:27.696667991Z","last_pushed","2019-05-31T10:17:10Z","os","linux","os_features","os_version","size","variant","2019-05-31T10:17:09.685838Z","last_updater","last_updater_username","media_type","latest","repository",7191832,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"routes/_layout.r.$namespace.$reponame.tags",{"_34":136,"_143":144,"_132":153,"_154":11},{"_36":137,"_38":138,"_41":42,"_43":44,"_45":11,"_46":47,"_48":49,"_50":139,"_53":31,"_28":29,"_54":55,"_56":40,"_57":58,"_59":60,"_61":62,"_63":-5,"_64":58,"_65":66,"_67":11,"_68":29,"_69":140,"_75":11,"_76":142,"_81":29,"_82":83},[],[40],[52],{"_71":11,"_72":141},[74],{"_78":17,"_79":11,"_80":11},"tags",{"_145":60,"_146":-5,"_147":-5,"_148":149},"count","next","previous","results",[150],{"_88":40,"_89":90,"_91":92,"_93":94,"_95":151,"_46":114,"_115":90,"_116":29,"_117":52,"_53":118,"_119":120,"_121":105,"_122":114,"_123":62,"_124":17},[152],{"_98":99,"_100":101,"_102":103,"_104":105,"_106":107,"_108":109,"_110":103,"_111":-5,"_112":92,"_59":62,"_113":-5},[],"canDeleteTags","actionData","errors"]

neebs42/nginx-proxy-manager

Tags for neebs42/nginx-proxy-manager