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

feat: disable self signed default certificate creation #1157

Merged
merged 1 commit into from
Oct 12, 2024

Conversation

buchdag
Copy link
Member

@buchdag buchdag commented Oct 4, 2024

This PR disable the self signed default certificate creation feature.

It can be re-enabled by setting CREATE_DEFAULT_CERTIFICATE to true on the acme-companion container.

This feature was added at a time when nginx-proxy had a bug that made it incorrectly serve (ie leak) the certificate for other domain(s) than the one that was request.

This is no longer the case, and forcing the creation of a self signed default certificate is now counter productive, with some users not understanding how they end up with a strange self signed certificate.

ping @pini-gh I think we discussed disabling this a few months ago but can't remember where.

@buchdag buchdag added the type/feat PR for a new feature label Oct 4, 2024
@buchdag buchdag self-assigned this Oct 4, 2024
@buchdag buchdag changed the title feat: remove default certificate creation feat: disable self signed default certificate creation Oct 4, 2024
@pini-gh
Copy link
Contributor

pini-gh commented Oct 10, 2024

ping @pini-gh I think we discussed disabling this a few months ago but can't remember where.

I don't remember either. But I agree that having a self signed default certificate does not help.

@buchdag buchdag merged commit 3cb7df6 into main Oct 12, 2024
36 checks passed
@buchdag buchdag deleted the remove-default-certificate branch October 12, 2024 17:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type/feat PR for a new feature
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants