NginxProxyManager / NginxProxyManager/nginx-proxy-manager
Error connection refused after update
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 34.2k
- Forks
- 3.9k
- Avg merge
- 21h 12m
- Merged PRs (30d)
- 20
Description
Hello,
I did some online search including ai bots but could not solve, so hope to find a solution here.
Running nginx proxy manager v2.9.15 with the simplest compose file (sql lite) in ubuntu 2004 LTS. After updating nginx container, I get connection refused. Below I type what I do and my findings
What I do;
docker-compose down
docker pull (no matter which version, even with v2.10.0 the same issue)
docker-compose up -d (--force-recreate)
Findings;
docker ps shows identical ports etc as before the update
In the container (docker exec -it nginx /bin/bash), the command curl -I http://localhost says connection failed on the port 80, connection refused after the update however before doing update, it works. So I'm assuming something is wrong with the webservice. As docker container environment is minimalistic, the commands I try, say command not found.
Docker logs say;
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service prepare: starting
❯ Configuring npmuser ...
id: 'npmuser': no such user
❯ Checking paths ...
❯ Setting ownership ...
chown: changing ownership of '/etc/nginx/conf.d': Read-only file system
s6-rc: warning: unable to start service prepare: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service prepare: starting
❯ Configuring npmuser ...
911
usermod: no changes
❯ Checking paths ...
❯ Setting ownership ...
chown: changing ownership of '/etc/nginx/conf.d': Read-only file system
s6-rc: warning: unable to start service prepare: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
Any further suggestions what could be wrong?
Update: Looks like after doing update, in the container there's no /etc/nginx/conf.d folder and files inside... Any suggestion how to solve?
Regards.
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 update with the reported docker-compose setup and compare the container logs before and after the update. Inspect the missing /etc/nginx/conf.d directory and the prepare service errors, especially the read-only filesystem and missing npmuser messages. Done means the container starts its services successfully and curl to localhost:80 succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, nginx, sqlite, ubuntu
- Domain
- backend, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100