-
Notifications
You must be signed in to change notification settings - Fork 3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error running notify command: nginx -s reload, exit status 1 #536
Comments
I thought the problem could be that compose creates networks for each compose file and nginx-proxy only connects to the default bridge. Therefore i connected nginx-proxy to all networks and used docker-compose restart.
|
I had the same issues, and the problem was exactly what you described. I solved it by creating a network called nginx-proxy:
Then I added the following to the bottom of my docker-compose file:
Here is my complete docker-compose.yml:
|
Closing as dup of #502 |
Hi,
i have a problem and no idea where to start debugging/i'm doing wrong.
I get the following log:
if remove the 9th container everything works (well, only the 9th has VIRTUAL_HOST set.)
This represents the docker-compose file of the 9th container.
I've noticed that the upstream block of mydomain.de is empty.
The text was updated successfully, but these errors were encountered: