Ensure erchef is configured to use custom nginx ports #832
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This should cover the case where a custom nginx ssl_port is specified, and should also handle when nginx is configured to not use SSL. A big thanks to @wduncanfraser for suggesting this fix! ChangeLog-Entry: [oc_erchef] [chef-server/50] Ensure erchef is configured to use custom nginx ports
|
I believe this is addressed by #833 and can be closed. |
|
@marcparadise Yup, looks like #833 might resolve what I was trying to fix. We'll give it a try once the next chef-server release comes out. |
|
Excellent, thanks for getting back to me! |
|
Not able to login if set custom nginx ssl port number When i login in chef UI i get this error 500Smell something burning?Sorry we have a small fire in the kitchen.An unexpected error has occurred. Our staff are manning the fire extinguishers and have been alerted. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request is intended to fix Issue #50 & is based on a workaround suggested by @wduncanfraser
This pull request should cover the case where a custom nginx ssl_port is specified,
and should also handle when nginx is configured to not use SSL.
Note: I'm not 100% sure what the
opscode-chef-mover.config.erbtemplate is used for, but I updated it to match theoc_erchef.config.erbchanges since the two files were very similar.