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: CHANGELOG.md
+16-1Lines changed: 16 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,21 @@
1
1
# Changelog
2
2
3
-
## v1.6.6-rc1 - ????/??/??
3
+
## v1.6.6-rc2 - ????/??/??
4
+
5
+
-[FEATURE] Refactor `Let's Encrypt` mail handling: validate the configured email and warn if missing/invalid. Use normal registration when valid; otherwise add **--register-unsafely-without-email** to Certbot and log that choice.
6
+
-[FEATURE] Add `DuckDNS` as a DNS provider in the `letsencrypt` plugin
7
+
-[FEATURE] Add `AUTH_BASIC_ROUNDS` setting to the `authbasic` plugin to configure password hashing strength (default: 656000, range: 1000-999999999).
8
+
-[FEATURE] Add new `mtls` plugin for mutual TLS client certificate authentication, allowing services to require and verify client certificates against trusted CA bundles with configurable verification modes, chain depth control, and optional header forwarding for downstream authorization.
9
+
-[AUTOCONF] Implement event debouncing in Docker, Ingress, and Swarm controllers for improved configuration management
10
+
-[MISC] Update default value for Permissions-Policy header to include additional features (`private-state-token-issuance` and `private-state-token-redemption`).
11
+
-[DEPS] Update coreruleset-v4 version to v4.20.0
12
+
-[DEPS] Updated luajit2 version to v2.1-20251030
13
+
-[DEPS] Updated lua-resty-core version to v0.1.32
14
+
-[DEPS] Updated lua-nginx-module version to v0.10.29
15
+
-[DEPS] Updated stream-lua-nginx-module version to v0.0.17
16
+
-[DEPS] Update lua-resty-openssl version to v1.7.0
17
+
18
+
## v1.6.6-rc1 - 2025/10/31
4
19
5
20
-[BUGFIX] Update BunkerWeb integration to use dedicated CrowdSec collection so that CrowdSec now works with the log format used by BunkerWeb.
6
21
-[FEATURE] Enhance plugin update process with per-plugin commit option and improved error handling
Copy file name to clipboardExpand all lines: docs/advanced.md
+38-38Lines changed: 38 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# Advanced usages
2
2
3
-
Many real-world use case examples are available in the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.6-rc1/examples) folder of the GitHub repository.
3
+
Many real-world use case examples are available in the [examples](https://github.com/bunkerity/bunkerweb/tree/v1.6.6-rc2/examples) folder of the GitHub repository.
4
4
5
-
We also provide numerous boilerplates, such as YAML files for various integrations and database types. These are available in the [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.6-rc1/misc/integrations) folder.
5
+
We also provide numerous boilerplates, such as YAML files for various integrations and database types. These are available in the [misc/integrations](https://github.com/bunkerity/bunkerweb/tree/v1.6.6-rc2/misc/integrations) folder.
6
6
7
7
This section only focuses on advanced usages and security tuning, see the [features section](features.md) of the documentation to see all the available settings.
8
8
@@ -87,7 +87,7 @@ You will find more settings about real IP in the [features section](features.md#
87
87
-p 80:8080/tcp \
88
88
-p 443:8443/tcp \
89
89
-p 443:8443/udp \
90
-
bunkerity/bunkerweb-all-in-one:1.6.6-rc1
90
+
bunkerity/bunkerweb-all-in-one:1.6.6-rc2
91
91
```
92
92
93
93
Please note that if your container is already created, you will need to delete it and recreate it so the new environment variables will be updated.
@@ -98,15 +98,15 @@ You will find more settings about real IP in the [features section](features.md#
98
98
99
99
```yaml
100
100
bunkerweb:
101
-
image: bunkerity/bunkerweb:1.6.6-rc1
101
+
image: bunkerity/bunkerweb:1.6.6-rc2
102
102
...
103
103
environment:
104
104
USE_REAL_IP: "yes"
105
105
REAL_IP_FROM: "1.2.3.0/24 100.64.0.0/10"
106
106
REAL_IP_HEADER: "X-Forwarded-For"
107
107
...
108
108
bw-scheduler:
109
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
109
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
110
110
...
111
111
environment:
112
112
USE_REAL_IP: "yes"
@@ -123,15 +123,15 @@ You will find more settings about real IP in the [features section](features.md#
123
123
124
124
```yaml
125
125
bunkerweb:
126
-
image: bunkerity/bunkerweb:1.6.6-rc1
126
+
image: bunkerity/bunkerweb:1.6.6-rc2
127
127
...
128
128
environment:
129
129
USE_REAL_IP: "yes"
130
130
REAL_IP_FROM: "1.2.3.0/24 100.64.0.0/10"
131
131
REAL_IP_HEADER: "X-Forwarded-For"
132
132
...
133
133
bw-scheduler:
134
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
134
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
135
135
...
136
136
environment:
137
137
USE_REAL_IP: "yes"
@@ -178,15 +178,15 @@ You will find more settings about real IP in the [features section](features.md#
178
178
179
179
```yaml
180
180
bunkerweb:
181
-
image: bunkerity/bunkerweb:1.6.6-rc1
181
+
image: bunkerity/bunkerweb:1.6.6-rc2
182
182
...
183
183
environment:
184
184
USE_REAL_IP: "yes"
185
185
REAL_IP_FROM: "1.2.3.0/24 100.64.0.0/10"
186
186
REAL_IP_HEADER: "X-Forwarded-For"
187
187
...
188
188
bw-scheduler:
189
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
189
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
190
190
...
191
191
environment:
192
192
USE_REAL_IP: "yes"
@@ -251,7 +251,7 @@ You will find more settings about real IP in the [features section](features.md#
251
251
-p 80:8080/tcp \
252
252
-p 443:8443/tcp \
253
253
-p 443:8443/udp \
254
-
bunkerity/bunkerweb-all-in-one:1.6.6-rc1
254
+
bunkerity/bunkerweb-all-in-one:1.6.6-rc2
255
255
```
256
256
257
257
Please note that if your container is already created, you will need to delete it and recreate it so the new environment variables will be updated.
@@ -262,7 +262,7 @@ You will find more settings about real IP in the [features section](features.md#
262
262
263
263
```yaml
264
264
bunkerweb:
265
-
image: bunkerity/bunkerweb:1.6.6-rc1
265
+
image: bunkerity/bunkerweb:1.6.6-rc2
266
266
...
267
267
environment:
268
268
USE_REAL_IP: "yes"
@@ -272,7 +272,7 @@ You will find more settings about real IP in the [features section](features.md#
272
272
...
273
273
...
274
274
bw-scheduler:
275
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
275
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
276
276
...
277
277
environment:
278
278
USE_REAL_IP: "yes"
@@ -290,7 +290,7 @@ You will find more settings about real IP in the [features section](features.md#
290
290
291
291
```yaml
292
292
bunkerweb:
293
-
image: bunkerity/bunkerweb:1.6.6-rc1
293
+
image: bunkerity/bunkerweb:1.6.6-rc2
294
294
...
295
295
environment:
296
296
USE_REAL_IP: "yes"
@@ -300,7 +300,7 @@ You will find more settings about real IP in the [features section](features.md#
300
300
...
301
301
...
302
302
bw-scheduler:
303
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
303
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
304
304
...
305
305
environment:
306
306
USE_REAL_IP: "yes"
@@ -352,7 +352,7 @@ You will find more settings about real IP in the [features section](features.md#
352
352
353
353
```yaml
354
354
bunkerweb:
355
-
image: bunkerity/bunkerweb:1.6.6-rc1
355
+
image: bunkerity/bunkerweb:1.6.6-rc2
356
356
...
357
357
environment:
358
358
USE_REAL_IP: "yes"
@@ -362,7 +362,7 @@ You will find more settings about real IP in the [features section](features.md#
362
362
...
363
363
...
364
364
bw-scheduler:
365
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
365
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
366
366
...
367
367
environment:
368
368
USE_REAL_IP: "yes"
@@ -514,7 +514,7 @@ To enable systemd-resolved as your DNS resolver in BunkerWeb, set the `DNS_RESOL
514
514
-p 80:8080/tcp \
515
515
-p 443:8443/tcp \
516
516
-p 443:8443/udp \
517
-
bunkerity/bunkerweb-all-in-one:1.6.6-rc1
517
+
bunkerity/bunkerweb-all-in-one:1.6.6-rc2
518
518
```
519
519
520
520
=== "Docker"
@@ -542,7 +542,7 @@ To enable systemd-resolved as your DNS resolver in BunkerWeb, set the `DNS_RESOL
542
542
- bw-dns
543
543
544
544
bunkerweb:
545
-
image: bunkerity/bunkerweb:1.6.6-rc1
545
+
image: bunkerity/bunkerweb:1.6.6-rc2
546
546
...
547
547
environment:
548
548
DNS_RESOLVERS: "dnsmasq"
@@ -553,7 +553,7 @@ To enable systemd-resolved as your DNS resolver in BunkerWeb, set the `DNS_RESOL
553
553
- bw-dns
554
554
555
555
bw-scheduler:
556
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
556
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
557
557
...
558
558
environment:
559
559
DNS_RESOLVERS: "dnsmasq"
@@ -667,7 +667,7 @@ Some integrations provide more convenient ways to apply configurations, such as
667
667
}" \
668
668
-p 80:8080/tcp \
669
669
-p 443:8443/tcp \
670
-
bunkerity/bunkerweb-all-in-one:1.6.6-rc1
670
+
bunkerity/bunkerweb-all-in-one:1.6.6-rc2
671
671
```
672
672
673
673
Please note that if your container is already created, you will need to delete it and recreate it for the new environment variables to be applied.
@@ -707,7 +707,7 @@ Some integrations provide more convenient ways to apply configurations, such as
707
707
-p 80:8080/tcp \
708
708
-p 443:8443/tcp \
709
709
-p 443:8443/udp \
710
-
bunkerity/bunkerweb-all-in-one:1.6.6-rc1
710
+
bunkerity/bunkerweb-all-in-one:1.6.6-rc2
711
711
```
712
712
713
713
=== "Docker"
@@ -730,7 +730,7 @@ Some integrations provide more convenient ways to apply configurations, such as
730
730
```yaml
731
731
...
732
732
bw-scheduler:
733
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
733
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
734
734
environment:
735
735
- |
736
736
CUSTOM_CONF_SERVER_HTTP_hello-world=
@@ -773,7 +773,7 @@ Some integrations provide more convenient ways to apply configurations, such as
773
773
774
774
```yaml
775
775
bw-scheduler:
776
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
776
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
777
777
volumes:
778
778
- ./bw-data:/data
779
779
...
@@ -843,7 +843,7 @@ Some integrations provide more convenient ways to apply configurations, such as
843
843
844
844
```yaml
845
845
bw-scheduler:
846
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
846
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
847
847
volumes:
848
848
- ./bw-data:/data
849
849
...
@@ -1073,7 +1073,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
1073
1073
-p 443:8443/udp \
1074
1074
-p 10000:10000/tcp \
1075
1075
-p 20000:20000/tcp \
1076
-
bunkerity/bunkerweb-all-in-one:1.6.6-rc1
1076
+
bunkerity/bunkerweb-all-in-one:1.6.6-rc2
1077
1077
```
1078
1078
1079
1079
Please note that if your container is already created, you will need to delete it and recreate it for the new environment variables to be applied.
@@ -1096,7 +1096,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
1096
1096
1097
1097
services:
1098
1098
bunkerweb:
1099
-
image: bunkerity/bunkerweb:1.6.6-rc1
1099
+
image: bunkerity/bunkerweb:1.6.6-rc2
1100
1100
ports:
1101
1101
- "80:8080" # Keep it if you want to use Let's Encrypt automation when using http challenge type
1102
1102
- "10000:10000" # app1
@@ -1111,7 +1111,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
1111
1111
- bw-services
1112
1112
1113
1113
bw-scheduler:
1114
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
1114
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
1115
1115
environment:
1116
1116
<<: *bw-api-env
1117
1117
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
@@ -1162,7 +1162,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
1162
1162
```yaml
1163
1163
services:
1164
1164
bunkerweb:
1165
-
image: bunkerity/bunkerweb:1.6.6-rc1
1165
+
image: bunkerity/bunkerweb:1.6.6-rc2
1166
1166
ports:
1167
1167
- "80:8080" # Keep it if you want to use Let's Encrypt automation when using http challenge type
1168
1168
- "10000:10000" # app1
@@ -1392,7 +1392,7 @@ For complete list of settings regarding `stream` mode, please refer to the [feat
1392
1392
```yaml
1393
1393
services:
1394
1394
bunkerweb:
1395
-
image: bunkerity/bunkerweb:1.6.6-rc1
1395
+
image: bunkerity/bunkerweb:1.6.6-rc2
1396
1396
ports:
1397
1397
# Keep it if you want to use Let's Encrypt automation when using http challenge type
1398
1398
- published: 80
@@ -1522,7 +1522,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
1522
1522
-p 80:8080/tcp \
1523
1523
-p 443:8443/tcp \
1524
1524
-p 443:8443/udp \
1525
-
bunkerity/bunkerweb-all-in-one:1.6.6-rc1
1525
+
bunkerity/bunkerweb-all-in-one:1.6.6-rc2
1526
1526
```
1527
1527
1528
1528
Please note that if your container is already created, you will need to delete it and recreate it for the new environment variables to be applied.
@@ -1566,7 +1566,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
1566
1566
1567
1567
services:
1568
1568
bunkerweb:
1569
-
image: bunkerity/bunkerweb:1.6.6-rc1
1569
+
image: bunkerity/bunkerweb:1.6.6-rc2
1570
1570
ports:
1571
1571
- "80:8080/tcp"
1572
1572
- "443:8443/tcp"
@@ -1581,7 +1581,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
1581
1581
- bw-services
1582
1582
1583
1583
bw-scheduler:
1584
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
1584
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
1585
1585
environment:
1586
1586
<<: *bw-api-env
1587
1587
BUNKERWEB_INSTANCES: "bunkerweb" # This setting is mandatory to specify the BunkerWeb instance
@@ -1675,7 +1675,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
1675
1675
1676
1676
services:
1677
1677
bunkerweb:
1678
-
image: bunkerity/bunkerweb:1.6.6-rc1
1678
+
image: bunkerity/bunkerweb:1.6.6-rc2
1679
1679
labels:
1680
1680
- "bunkerweb.INSTANCE=yes"
1681
1681
environment:
@@ -1688,7 +1688,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
1688
1688
- bw-services
1689
1689
1690
1690
bw-scheduler:
1691
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
1691
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
1692
1692
environment:
1693
1693
<<: *bw-api-env
1694
1694
BUNKERWEB_INSTANCES: "" # We don't need to specify the BunkerWeb instance here as they are automatically detected by the autoconf service
@@ -1703,7 +1703,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
1703
1703
- bw-db
1704
1704
1705
1705
bw-autoconf:
1706
-
image: bunkerity/bunkerweb-autoconf:1.6.6-rc1
1706
+
image: bunkerity/bunkerweb-autoconf:1.6.6-rc2
1707
1707
depends_on:
1708
1708
- bunkerweb
1709
1709
- bw-docker
@@ -1943,7 +1943,7 @@ BunkerWeb supports PHP using external or remote [PHP-FPM](https://www.php.net/ma
1943
1943
```yaml
1944
1944
services:
1945
1945
bunkerweb:
1946
-
image: bunkerity/bunkerweb:1.6.6-rc1
1946
+
image: bunkerity/bunkerweb:1.6.6-rc2
1947
1947
volumes:
1948
1948
- /shared/www:/var/www/html
1949
1949
...
@@ -2042,7 +2042,7 @@ By default, BunkerWeb will only listen on IPv4 addresses and won't use IPv6 for
2042
2042
```yaml
2043
2043
services:
2044
2044
bw-scheduler:
2045
-
image: bunkerity/bunkerweb-scheduler:1.6.6-rc1
2045
+
image: bunkerity/bunkerweb-scheduler:1.6.6-rc2
2046
2046
environment:
2047
2047
USE_IPv6: "yes"
2048
2048
@@ -2101,7 +2101,7 @@ You can configure the logging driver for your services in your `docker-compose.y
0 commit comments