-
Notifications
You must be signed in to change notification settings - Fork 156
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
Nginx container fails intermittently on startup when not using letsencrypt #25
Comments
issa-tseng
added a commit
that referenced
this issue
Oct 11, 2018
* as far as i can tell, this happens when auto_enable_configs comes up empty, and nginx tries to start with nothing enabled, and it causes unhappiness. * i'm not completely sure. * this little workaround creates a dummy server (that isn't exposed outside of the container at all) that doesn't require SSL at all, and so it should always be enabled and start up. * maybe it works, maybe it doesn't.
issa-tseng
added a commit
that referenced
this issue
Oct 11, 2018
* as far as i can tell, this happens when auto_enable_configs comes up empty, and nginx tries to start with nothing enabled, and it causes unhappiness. * i'm not completely sure. * this little workaround creates a dummy server (that isn't exposed outside of the container at all) that doesn't require SSL at all, and so it should always be enabled and start up. * maybe it works, maybe it doesn't.
issa-tseng
added a commit
that referenced
this issue
Oct 17, 2018
* this time we just start nginx directly if the SSL type is anything other than letsencrypt.
issa-tseng
added a commit
that referenced
this issue
Oct 23, 2018
bug #25: second attempt to deal with nginx boot problems.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As seen by me in dev env with self-signed certs and by Matthew MacGregor (ref) with a custom local ssl cert.
The text was updated successfully, but these errors were encountered: