You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[](https://public.jc21.com/nginx-proxy-manager/v2/large/access-lists-new1.jpg)
By far the easiest way to get up and running. Create this `docker-compose.yml`
36
-
37
-
```yml
38
-
version: "2"
39
-
services:
40
-
app:
41
-
image: jc21/nginx-proxy-manager
42
-
restart: always
43
-
ports:
44
-
- 80:80
45
-
- 81:81
46
-
- 443:443
47
-
volumes:
48
-
- ./config:/config
49
-
- ./letsencrypt:/etc/letsencrypt
50
-
```
54
+
Please consult the [installation instructions](doc/INSTALL.md) for a complete guide or
55
+
if you just want to get up and running in the quickest time possible, grab all the files in the `doc/example/` folder and run `docker-compose up -d`
51
56
52
-
Then:
53
57
54
-
```bash
55
-
docker-compose up -d
56
-
```
58
+
## Importing from Version 1?
57
59
60
+
Here's a [guide for you to migrate your configuration](doc/IMPORTING.md). You should definitely read the [installation instructions](doc/INSTALL.md) first though.
58
61
59
-
### Method 2: Using vanilla docker
62
+
**Why should I?**
60
63
61
-
```bash
62
-
docker run -d \
63
-
-p 80:80 \
64
-
-p 81:81 \
65
-
-p 443:443 \
66
-
-v /path/to/config:/config \
67
-
-v /path/to/letsencrypt:/etc/letsencrypt \
68
-
--restart always \
69
-
jc21/nginx-proxy-manager
70
-
```
64
+
Version 2 has the following improvements:
65
+
66
+
- Management security and multiple user access
67
+
- User permissions and visibility
68
+
- Custom SSL certificate support
69
+
- Audit log of changes
70
+
- Broken nginx config detection
71
+
- Multiple domains in Let's Encrypt certificates
72
+
- Wildcard ___domain name support (not available with a Let's Encrypt certificate though)
73
+
- It's super sexy
71
74
72
75
73
76
### Raspberry Pi / ARMHF
@@ -87,16 +90,21 @@ docker run -d \
87
90
88
91
## Administration
89
92
90
-
Now that your docker container is running, connect to it on port `81` for the admin interface.
93
+
When your docker container is running, connect to it on port `81` for the admin interface.
91
94
92
95
[http://localhost:81](http://localhost:81)
93
96
94
-
There is no authentication on this interface to keep things simple. It is expected that you would not
95
-
expose port 81 to the outside world.
97
+
Note: Requesting SSL Certificates won't work until this project is accessible from the outside world, as explained below.
96
98
97
-
From here, the rest should be self explanatory.
98
99
99
-
Note: Requesting SSL Certificates won't work until this project is accessible from the outside world, as explained below.
0 commit comments