starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 09:25:55 +03:00

[GH-ISSUE #3731] Toggling "HSTS Enabled" leads to "Unknown hsts_header variable" error with proxy offline #2461

New issue

Open

opened 2026-02-26 07:35:39 +03:00 by kerem · 6 comments

kerem commented

2026-02-26 07:35:39 +03:00

Owner

Originally created by @NeoMod on GitHub (May 1, 2024).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3731

Checklist

Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
- Yes
Are you sure you're not using someone else's docker image?
- Yes
Have you searched for similar issues (both open and closed)?
- Yes

Describe the bug

This seems, feels, and behaves like yet another error related to the plethora of issues reported with the version 2.11.0 and 2.11.1 but with another presentation.

Upon creation of a new "Proxy Host", without even accessing the "Custom Location" tab neither setting one, enabling the option "HSTS Enabled" in the "SSL" Section leads to an "Offline Status" with the following error: "unknown hsts_header variable".

I have already mounted an empty "_hsts_map.conf" at the "/app/templates/" path inside the container without any luck; disabling the "HSTS Enabled" toggle brings the host immediately on-line, working as expected.
I am using Cloudflare, both as domain registar with DNS managment and SSL Certificate Provider, with proper SSL and HSTS settings.

On a similar machine, using the previous NPM version (2.10.4) - as many other users mentioned - solved the issue.

Nginx Proxy Manager Version
V. 2.11.1 (tested and confirmed also with 2.11.0)

To Reproduce
Steps to reproduce the behavior:

Go to 'Proxy Hosts'
Click on 'Add Proxy Host'
Compile the "Details" tab as requested
Select a valid "Access List" option (in my setup, a Cloudflare ip-allow list)
Click on the "SSL" tab
Select the correct SSL Certificate
Enable the "Force SSL", "HTTP/2 Support" and "HSTS Enabled" options
Click on "Save"
Verify that the newly created Proxy Host is marked as "Offline" with the error reported above.

Additionally, upon deleting the above-created entry, docker logs for the container show an error about a file deletion:

[05/01/2024] [2:52:40 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[05/01/2024] [2:52:40 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf
[05/01/2024] [2:52:40 PM] [Global   ] › ⬤  debug     CMD: /usr/sbin/nginx -t -g "error_log off;"
[05/01/2024] [2:52:40 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/1.conf
[05/01/2024] [2:52:40 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
  "errno": -2,
  "code": "ENOENT",
  "syscall": "unlink",
  "path": "/data/nginx/proxy_host/1.conf"
}

Instead, on Version 2.10.4 the Log shows something a bit different, as soon as the Proxy Host is created altough it seems to be working as expected:

Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0
[5/1/2024] [2:55:01 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/2.conf
[5/1/2024] [2:55:01 PM] [Nginx    ] › ⬤  debug     Could not delete file: {
  "errno": -2,
  "syscall": "unlink",
  "code": "ENOENT",
  "path": "/data/nginx/proxy_host/2.conf"
}
[5/1/2024] [2:55:01 PM] [Nginx    ] › ℹ  info      Reloading Nginx
[5/1/2024] [2:55:01 PM] [Nginx    ] › ⬤  debug     Deleting file: /data/nginx/proxy_host/2.conf
[5/1/2024] [2:55:01 PM] [Nginx    ] › ℹ  info      Reloading Nginx

Expected behavior
The "Proxy Host" should be created without issues even with the "HSTS Support" enabled.

Screenshots

Operating System
Docker version 26.1.0, build 9714adc
Debian GNU/Linux 11 (bullseye)

Additional context
Somehow it seems related to the following: #3474 #3678 #3484 #3512
Users have shared many different approaches to try and fix the issue in the comments, altough the results seems to vary; the consensus verges toward downgrading to v.2.10.4 to restore functionality.

Originally created by @NeoMod on GitHub (May 1, 2024). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3731 **Checklist** - Have you pulled and found the error with `jc21/nginx-proxy-manager:latest` docker image? - Yes - Are you sure you're not using someone else's docker image? - Yes - Have you searched for similar issues (both open and closed)? - Yes **Describe the bug** This _seems_, _feels_, and _behaves_ like yet another error related to the plethora of issues reported with the version 2.11.0 and 2.11.1 but with another presentation. Upon creation of a new "Proxy Host", without even accessing the "Custom Location" tab neither setting one, enabling the option "HSTS Enabled" in the "SSL" Section leads to an "Offline Status" with the following error: "unknown hsts_header variable". <img width="255" alt="image" src="https://github.com/NginxProxyManager/nginx-proxy-manager/assets/13747261/64536de5-14fe-462c-9949-6e2cdee6e5a6"> I have already mounted an empty "_hsts_map.conf" at the "/app/templates/" path inside the container without any luck; disabling the "HSTS Enabled" toggle brings the host immediately on-line, working as expected. I am using Cloudflare, both as domain registar with DNS managment and SSL Certificate Provider, with proper SSL and HSTS settings. On a similar machine, using the previous NPM version (2.10.4) - as many other users mentioned - solved the issue. **Nginx Proxy Manager Version** V. 2.11.1 (tested and confirmed also with 2.11.0) **To Reproduce** Steps to reproduce the behavior: 1. Go to 'Proxy Hosts' 2. Click on 'Add Proxy Host' 3. Compile the "Details" tab as requested 4. Select a valid "Access List" option (in my setup, a Cloudflare ip-allow list) 5. Click on the "SSL" tab 6. Select the correct SSL Certificate 7. Enable the "Force SSL", "HTTP/2 Support" and "HSTS Enabled" options 8. Click on "Save" 9. Verify that the newly created Proxy Host is marked as "Offline" with the error reported above. Additionally, upon deleting the above-created entry, docker logs for the container show an error about a file deletion: ``` [05/01/2024] [2:52:40 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [05/01/2024] [2:52:40 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [05/01/2024] [2:52:40 PM] [Global ] › ⬤ debug CMD: /usr/sbin/nginx -t -g "error_log off;" [05/01/2024] [2:52:40 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/1.conf [05/01/2024] [2:52:40 PM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "code": "ENOENT", "syscall": "unlink", "path": "/data/nginx/proxy_host/1.conf" } ``` Instead, on Version 2.10.4 the Log shows something a bit different, as soon as the Proxy Host is created altough it seems to be working as expected: ``` Duplicate relation "access_list" in a relation expression. You should use "a.[b, c]" instead of "[a.b, a.c]". This will cause an error in objection 2.0 [5/1/2024] [2:55:01 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/2.conf [5/1/2024] [2:55:01 PM] [Nginx ] › ⬤ debug Could not delete file: { "errno": -2, "syscall": "unlink", "code": "ENOENT", "path": "/data/nginx/proxy_host/2.conf" } [5/1/2024] [2:55:01 PM] [Nginx ] › ℹ info Reloading Nginx [5/1/2024] [2:55:01 PM] [Nginx ] › ⬤ debug Deleting file: /data/nginx/proxy_host/2.conf [5/1/2024] [2:55:01 PM] [Nginx ] › ℹ info Reloading Nginx ``` **Expected behavior** The "Proxy Host" should be created without issues even with the "HSTS Support" enabled. **Screenshots** **Operating System** Docker version 26.1.0, build 9714adc Debian GNU/Linux 11 (bullseye) **Additional context** Somehow it seems related to the following: #3474 #3678 #3484 #3512 Users have shared many different approaches to try and fix the issue in the comments, altough the results seems to vary; the consensus verges toward downgrading to v.2.10.4 to restore functionality.

kerem added the

stale

bug

labels

2026-02-26 07:35:39 +03:00

kerem commented

2026-02-26 07:35:40 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Dec 27, 2024):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Dec 27, 2024): Issue is now considered stale. If you want to keep it open, please comment :+1:

kerem commented

2026-02-26 07:35:40 +03:00

Author

Owner

@NeoMod commented on GitHub (Dec 27, 2024):

Still an issue one month after publishing this report; moved away from NPM since then. I'm closing this, unfortunately with no solution for the next person whom shall find this post.

@NeoMod commented on GitHub (Dec 27, 2024): Still an issue one month after publishing this report; moved away from NPM since then. I'm closing this, unfortunately with no solution for the next person whom shall find this post.

kerem commented

2026-02-26 07:35:40 +03:00

Author

Owner

@Daronsong commented on GitHub (Jun 28, 2025):

Can this please be reopened, I still have this issue!

@Daronsong commented on GitHub (Jun 28, 2025): Can this please be reopened, I still have this issue!

kerem commented

2026-02-26 07:35:40 +03:00

Author

Owner

@NeoMod commented on GitHub (Jun 29, 2025):

Can this please be reopened, I still have this issue!

@Daronsong, I will reopen the issue, but I don't know how helpful it could be since I don't have any means to test it further, since I changed the software.

@NeoMod commented on GitHub (Jun 29, 2025): > Can this please be reopened, I still have this issue! @Daronsong, I will reopen the issue, but I don't know how helpful it could be since I don't have any means to test it further, since I changed the software.

kerem commented

2026-02-26 07:35:40 +03:00

Author

Owner

@Daronsong commented on GitHub (Jun 29, 2025):

I’m having a similar issue where toggling hsts causes the host to become offline and unreachable, and could continue testing.

Devon Bisaillon
@.***
(705) 618-2679

On Jun 29, 2025, at 10:12 AM, NeoMod @.***> wrote:

Reopened #3731 https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3731.

—
Reply to this email directly, view it on GitHubhttps://github.com/NginxProxyManager/nginx-proxy-manager/issues/3731#event-18374401404, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACADZGWFO4YWRAGZT5XWQVT3F7X5LAVCNFSM6AAAAABUH6EF7SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJYGM3TINBQGE2DANA.
You are receiving this because you were mentioned.Message ID: @.***>

@Daronsong commented on GitHub (Jun 29, 2025): I’m having a similar issue where toggling hsts causes the host to become offline and unreachable, and could continue testing. Devon Bisaillon ***@***.*** (705) 618-2679 On Jun 29, 2025, at 10:12 AM, NeoMod ***@***.***> wrote: Reopened #3731<https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3731>. — Reply to this email directly, view it on GitHub<https://github.com/NginxProxyManager/nginx-proxy-manager/issues/3731#event-18374401404>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ACADZGWFO4YWRAGZT5XWQVT3F7X5LAVCNFSM6AAAAABUH6EF7SVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJYGM3TINBQGE2DANA>. You are receiving this because you were mentioned.Message ID: ***@***.***>

kerem commented

2026-02-26 07:35:40 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 18, 2026):

Issue is now considered stale. If you want to keep it open, please comment 👍

@github-actions[bot] commented on GitHub (Jan 18, 2026): Issue is now considered stale. If you want to keep it open, please comment :+1:

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#2461

No description provided.

Rows
Columns