NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Error after updating - map not allowed here
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Checklist
- Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker 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:
- Update to latest
- Edit any host
- Save
- See error
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the generated _hsts_map.conf and the Nginx error in /var/log/nginx/error.log; reproduce the failure using docker compose pull && docker compose up -d, then edit and save a host with a custom location. Trace why the map block is appended there, and consider the issue done when the generated configuration reloads successfully without manual edits after a restart.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, nginx
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100