chef / chef/chef-server

Not able to login to in Chef UI for custom ngnix ssl port

Open
#1,057 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Aspect: Integration Component: chef-manage Status: Sustaining Backlog Triage: Try Reproducing Type: Bug
Dominant language
Erlang
Stars
303
Forks
211
Avg merge
1d 8h
Merged PRs (30d)
5

Description

Chef Server Version : chef-server 12.11.1
Not able to login if set custom nginx ssl port number
/etc/opscode/chef-server.rb
nginx['ssl_port']=8444
bookshelf['vip_port'] = 8444

When i login in from chef UI i get this error

500 Smell 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.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the reported configuration in /etc/opscode/chef-server.rb, especially nginx['ssl_port'] and bookshelf['vip_port'], and reproduce the Chef UI login failure on port 8444. Trace the login request until the 500 error occurs and compare it with the default SSL port behavior. Done means Chef UI login succeeds when both custom ports are configured.

Written by the indexing model from the issue text.

Assessment

Tech stack
nginx
Domain
authentication, backend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.