Unfortunately, I wasn’t able to wait any longer for a response so I ended up having to setup a new server and move everything over. Just sucks that it happened on the “stable” release.
hey, thanks for the solution guys!! i was also looking for the same and it was helpful.
That nginx_proxy container has always given problems, not just in version 4.0.12.
For me it worked to stop the container with
docker stop CONTAINER-ID and another
docker start CONTAINER-ID . Hope this will help anyone else having this issue.