-
Notifications
You must be signed in to change notification settings - Fork 18
feat(nginx-proxy): Implement ssl_reject_handshake for missing certificates #300
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
Open
mrrobot47
wants to merge
1
commit into
develop
Choose a base branch
from
feat/nginx-proxy-ssl-reject-handshake
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+31
−2
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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 file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The condition change creates a server block for all vhosts where
$is_httpsis false and$https_methodis not 'nohttps', regardless of whether any certificates exist. This means a fallback HTTPS server block will be created even when$https_methodis 'redirect' or 'noredirect' and no default certificate exists. Whenssl_reject_handshake on;is used, the server block still requireslisten 443 ssl, but nginx may fail to start if there's no certificate at all to bind to the SSL context. The old condition ensured this block was only created when default certificates existed, preventing this issue.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for catching this! You're absolutely right -
ssl_reject_handshake on;still requires a valid SSL context to bind the socket, so nginx would fail to start without any certificate.I've applied your suggested fix in commit 9b7fb39:
ssl_reject_handshakelogic entirelyThe behavior is now:
This prevents nginx startup failures while maintaining the improved 503 status code.