Error after updating - map not allowed here

[daedric7]

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

After updating NPM ( docker compose pull && docker compose up -d) everything was OK until i edited a host.

After that the host started failing. After some debug i found a entry in /var/log/nginx/error.log stating

"map not allowed here"

I managed to find the map entry in the middle of the conf and it's this:

  map $scheme $hsts_header {
    https   "max-age=63072000; preload";
}

This is suffixed on each of my custom locations for that host.

I edited the _hsts_map.conf to comment them and the error was solved, but this won't survive a docker restart.

Nginx Proxy Manager Version

v2.11.0 © 2024 jc21.com.

To Reproduce
Steps to reproduce the behavior:

1. Update to latest
2. Edit any host
3. Save
4. See error

[Kingi-s]

I just did a fresh install of npm and the custom locations also dont work for me.
edit:
downgrading to 2.10.4 fixed the issue for now.

[exenza]

Have same issue, the error is actually visible as well in the UI

[daedric7]

Have same issue, the error is actually visible as well in the UI

Question:

How did you get that error popup ? I had to go miles to figure out what the error was :)

[Kingi-s]

Have same issue, the error is actually visible as well in the UI

Question:

How did you get that error popup ? I had to go miles to figure out what the error was :)

Hover your mouse over the red ball before the Offline text. i also found it by accident.

[daedric7]

Workaround:

create empty file named _hsts_map.conf on the same dir as docker-compose.yaml.

Add this line to the volumes of docker-compose.yaml :

- ./_hsts_map.conf:/app/templates/_hsts_map.conf

[573dave]

Same issue here. And since I'm using unraid I can't figure out the workaround.

[UlfR]

Same for me "map directive is not allowed here" if add custom location

[daedric7]

Same issue here. And since I'm using unraid I can't figure out the workaround.

All we are doing is mounting a empty file from the host into tha container dir that has the problematic file, thereby making it empty as well and bypassing the issue.

Can you replicate it?

[ghTravis]

Also experiencing the same issue here. Just tried to add a new proxy host with custom locations. Appearing Offline.

[rasturic]

jc21/nginx-proxy-manager:github-pr-3478 fixes it for me.

[aphex3k]

When running as part of TrueNAS Scale Apps (in k8s), the included configuration UI doesn't allow for adding a custom volume so the suggested workaround can not be applied.

- ./_hsts_map.conf:/app/templates/_hsts_map.conf

Changing the tag from latest is also not possible, so one can not roll-back to a previous version or test the custom resource location.

This breaks custom locations on TrueNAS without fix for now.