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
Copy file name to clipboardExpand all lines: README.md
+7-3Lines changed: 7 additions & 3 deletions
Original file line number
Diff line number
Diff line change
@@ -13,10 +13,14 @@
13
13
</a>
14
14
</p>
15
15
16
-
# Trivy Scan
16
+
# Trivy Scan (CVE scanner)
17
17
-[Buster-slim based image](https://trivy.dev/results/?image=baudneo/nginx-proxy-manager:latest)
18
18
-[Bullseye-slim based image](https://trivy.dev/results/?image=baudneo/nginx-proxy-manager:bullseye)
19
19
---
20
+
21
+
# Updated
22
+
- Now running Debian Bullseye as base OS.
23
+
---
20
24
This project comes as a pre-built docker image that enables you to easily forward to your websites
21
25
running at home or otherwise, including free SSL, without having to know too much about Nginx or Letsencrypt.
22
26
@@ -66,7 +70,7 @@ I won't go in to too much detail here but here are the basics for someone new to
66
70
version: '3'
67
71
services:
68
72
app:
69
-
image: 'baudneo/nginx-proxy-manager:latest'
73
+
image: 'baudneo/nginx-proxy-manager:bullseye'
70
74
restart: unless-stopped
71
75
ports:
72
76
- '80:80'
@@ -140,7 +144,7 @@ Immediately after logging in with this default user you will be asked to modify
140
144
# ModSecurity
141
145
_ModSecurity WAF is installed and loaded by default, OWASP-CoreRuleSet is installed and used as the default rule set. The user is responsible for configuring modsecurity via config/CLI._
142
146
143
-
__MODSECURITY HAS KNOWN MEMORY LEAKS!__ Whenever `nginx -s reload` is issued expect RAM to increase by 10 to several hundred MB (depending on if you have custom rule files or are double enabling modsec). Nginx is reloaded every time a host is created/modified and when the SSL cert renewal timer resets. The only way to get modsec to release REAM is to restart nginx from inside the running container using `nginx -s stop; nginx -s reload` or by restarting the container using `sudo docker restart [Name of NPM container]`
147
+
__MODSECURITY HAS KNOWN MEMORY LEAKS!__ Whenever `nginx -s reload` is issued expect RAM to increase by 10 to several hundred MB (depending on if you have custom rule files or are double enabling modsec). Nginx is reloaded every time a host is created/modified and when the SSL cert renewal timer resets. The only way to get modsec to release RAM is to restart nginx from inside the running container using `nginx -s stop; nginx -s reload` or by restarting the container using `sudo docker restart [Name of NPM container]`
144
148
145
149
## Environment Variables
146
150
-`MODSEC_CREATE=1` - Force recreating the default modsecurity config, _This should never be needed_
0 commit comments