-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Connection refused #26
Comments
Hi, I have the same issue, how did you managed to correct it? |
Having the same issue as above @melvinmajor |
I'm also getting similar errors.
I have the feeling the server with docker-compose doesn't start correctly. But I have no idea how to check this or how to fix it |
My setup: Running with upstream node apps. The error I was getting when I ran So I first mounted the nginx access and error logs to a volume and it always showed 1 of 2 things
-> The certificate error made sense as it did not exist and hence this error occured SOLUTION My nginx server had no clue about the "auth" upstream as it would only be available when my docker service - "auth" would be up. So after a lot of ignoring the error, I just ran docker-compose up before the Voila solved my issue. Hope my stupidness helps others hours of googling. Cheers! |
The text was updated successfully, but these errors were encountered: