Skip to content
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

Ensure erchef is configured to use custom nginx ports #832

Closed

Conversation

metavida
Copy link

@metavida metavida commented May 6, 2016

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.erb template is used for, but I updated it to match the oc_erchef.config.erb changes since the two files were very similar.

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
@marcparadise
Copy link
Member

I believe this is addressed by #833 and can be closed.

@metavida
Copy link
Author

@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.

@metavida metavida closed this May 23, 2016
@metavida metavida deleted the s3_url_with_nonstandard_ssl_port branch May 23, 2016 16:21
@marcparadise
Copy link
Member

Excellent, thanks for getting back to me!

@dixon1234
Copy link

Not able to login if set custom nginx ssl port number
nginx['ssl_port']=8444
bookshelf['vip_port'] = 8444

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
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants