mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2795] nginx-proxy-manager run inside docker doesn't work after reboot machine #1921
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#1921
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ArchMatt-GraveKeeper on GitHub (Apr 2, 2023).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2795
Hi, i have a problem with proxy-manager, after restart of server the proxy manager running but not propertly, container is up, docker said, also portainer. If you connect localy to portainer you can see everything is alright but it isnt.
I cannot access any web page, even not the nginx host him self even not localy, but everything is alright if i do manual restart of container.
then everything work alright.
Running RHEL 9.1, with SElinux enable, docker with compose latest.
Can anyone tell what should i try ?
Already tried changing restart policy of container from unless stopped to always but this even not working.
Thanks for your support !
@jackblk commented on GitHub (Apr 3, 2023):
Yup, having same issue for 2 days straight. Probably related to new release 2.10.2.
Here's my log
@upuldi commented on GitHub (Apr 3, 2023):
I am having the same issue. Is there a solution for this ?
@warlordattack commented on GitHub (Apr 3, 2023):
same here with docker inside ds918+ nas
@upuldi commented on GitHub (Apr 3, 2023):
As many have suggested reverting it to the previous 2.9.22 did the trick for me.
@X4V1 commented on GitHub (Apr 4, 2023):
same here from a raspberry pi
@bleomycin commented on GitHub (Apr 4, 2023):
Same :(
@Norsagir commented on GitHub (Apr 5, 2023):
+1
@vacances commented on GitHub (Apr 5, 2023):
Same thing, however it works after container recreation. I don't really want to force restart it manually on every update/reboot of machine tbh.
@Xer69 commented on GitHub (Apr 6, 2023):
same here on raspberryPI 4 64x.
add to rollback to 2.9.22 cause even container recreation didn't do the trick.
@EgonHeuson commented on GitHub (Apr 7, 2023):
Hello!
Same here. If it can help, I think this has something to do with the creation of the npm user as I quite oftne get an error with this step in the logs. Although the last time I got these logs:
❯ Configuring npmuser ... 0 usermod: no changes ❯ Checking paths ... ❯ Setting ownership ... s6-rc: fatal: timed out s6-sudoc: fatal: unable to get exit status from server: Operation timed out /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.I have to add up that this doesn't appear with all my npm instances. On some of my VMs I have the issue, and on some I don't. Hard for me to understand...
@nocomment-bln commented on GitHub (Apr 7, 2023):
Same problem here
@anthonws commented on GitHub (Apr 8, 2023):
I also experienced this yesterday, as I had to restart my entire NAS (Synology), but I was already running 2.9.22 (snap to image version).
@danielowen777 commented on GitHub (Apr 8, 2023):
I am experiencing same issue running on Ubuntu LTS 22.02. Restarting the container fixes it but no use if the server power cycles as requires manual restart. I have rolled back to 2.9.22 and all working perfectly.
@meckitt commented on GitHub (Apr 8, 2023):
Have the same issue... Rolled back to 2.9.22 aswell
@ScottSucksAtProgramming commented on GitHub (Apr 14, 2023):
I found a way to fix this on my install. Hopefully what I did might help. You can take a look at my post here: Doesn't work after reboot #106
@bleomycin commented on GitHub (Apr 21, 2023):
Unfortunately this didn't work for me :(
@arthurgeek commented on GitHub (Apr 24, 2023):
even rolling back to
2.9.22doesn't fix the issue for me. nginx can be started If container is recreated, but can't start after reboot. I had some power issues at home and noticed this every single time :(.@KenzoB73 commented on GitHub (May 3, 2023):
Same here, 2.9.22 didn't fix it, but removal and recreation of the container works.
@brianjw commented on GitHub (May 3, 2023):
Running NPM 2.10.2 on a Synology DS 218+ in a docker container - same issue as everyone else. After reboot, NPM is throwing errors and won't start properly. After removing the container and recreating it, everything is working again.
@rymancl commented on GitHub (May 3, 2023):
Good suggestion. In my case, you don't even have to remove and recreate the container. Running a
docker-compose restarton the NPM service is plenty. I run this after my standarddocker-compose upfor the whole stack.@arthurgeek commented on GitHub (May 8, 2023):
Are there any fix to this?
@redtripleAAA commented on GitHub (May 9, 2023):
I have this instance running for many years, after rebooting the host. The host started.
Note: using this tag fixed the issue for me for now # 2.9.22
@arthurgeek commented on GitHub (May 21, 2023):
fixed with v2.10.3.
@brianjw commented on GitHub (May 23, 2023):
Confirmed fixed on my end with 2.10.3 as well.
@flygav1 commented on GitHub (Jun 11, 2024):
still not fixed
@Fernando123Duran commented on GitHub (Aug 14, 2024):
The problem persists in version 2.11.0 and 2.11.3, the latest to date.
Any solution?
@rpgdev commented on GitHub (Aug 23, 2024):
Why was this closed if it's still happening? I restart the container to back it up and usually the first few times I access it it plainly don't work until after I manually hit the nginxpm web admin interface.. then it "wakes up" and I'm able to access the other addresses it serves once more.
@rpgdev commented on GitHub (Aug 23, 2024):
I tried this and can confirm for this thread that it works (so far).
@eniskastrati commented on GitHub (Dec 14, 2024):
Still not working for me:
Temporary Solution for my server was to add to the crontab:
@reboot docker compose -f /path/to/file.yaml up -d
@rpgdev commented on GitHub (Dec 14, 2024):
@eniskastrati have you pulled the latest image? I removed the workaround and updated the image and it hasn't happened again.
@eniskastrati commented on GitHub (Dec 18, 2024):
Well it was just a mistake from me.
I had to define restart: always instead of restart: unless-stopped. During shutdown the docker daemon stops all of the services and will not start them again.
Also the documentation for this Restart Policy Docker.
@DoctorS commented on GitHub (Jan 16, 2025):
Make sure that native nginx is not using the same port. It can auto-start after a reboot.