NginxProxyManager / NginxProxyManager/nginx-proxy-manager
unable to start/run after updating to 2.14.0
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 to 2.14, NPM no longer functions. i cannot access the web UI nor is it proxying requests to existing hosts.
Nginx Proxy Manager Version
cannot get to login page
To Reproduce
Steps to reproduce the behavior:
- Update image to 2.14 (from a recent version, unfortunately i'm not sure which one)
- cannot get to web UI, no functioning proxy hosts.
Expected behavior
Screenshots
Operating System
Ubuntu 20.04
Additional context
Docker 28.1.1
From the docker logs:
nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /data/nginx/proxy_host/1.conf:19
nginx: [warn] protocol options redefined for 0.0.0.0:443 in /data/nginx/proxy_host/11.conf:14
^^^those entries repeated for other configured hosts.
nginx: [emerg] unknown "x_forwarded_scheme" variable
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
Reproduce the update to the jc21/nginx-proxy-manager:latest image at version 2.14 on Ubuntu 20.04 and start with the Docker logs. Inspect the generated files under /data/nginx/proxy_host/, especially 1.conf and 11.conf, around the unknown x_forwarded_scheme variable. Done means the container starts, the web UI is reachable, and existing proxy hosts work without this emerg error.
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
- Needs clarification
- Newbie friendliness
- 35/100