NginxProxyManager / NginxProxyManager/nginx-proxy-manager
[RouterOS] a duplicate default server for 0.0.0.0:81 in /etc/nginx/conf.d/production.conf
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
I'm trying to run the docker on a Mikotik RB5009 running RouterOS 7.11 and the container fails to start with error:
nginx: [emerg] a duplicate default server for 0.0.0.0:81 in /etc/nginx/conf.d/production.conf:3
I can get the container running by deleting the file /etc/nginx/conf.d/dev.conf but I don't think this is the right way to get this working.
Nginx Proxy Manager Version
2.10.4 (ARM64)
To Reproduce
Steps to reproduce the behavior:
- pull docker container in RouterOS
- Start it with logging enabled
- See error in log
Expected behavior
nginx starts
Operating System
RouterOS 7.11 (ARM64)
Additional context
I had this container running fine on this platform for months but a recent update changed something. I'm not sure if an NPM or RouterOS update is the cause. Also, the container runs without issue with the dev.conf file removed.
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 by reproducing the startup failure on RouterOS 7.11 ARM64 with the jc21/nginx-proxy-manager:latest image and inspect the logged error. Compare /etc/nginx/conf.d/dev.conf with /etc/nginx/conf.d/production.conf, especially the default server definitions on port 81. Done means the container starts with both configuration files present and nginx no longer reports a duplicate default server.
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
- 32/100