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.

Sign up for GitHub

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

Jump to bottom

Broken TLS when TLS_CERT_EMAIL uses an invalid domain name #66

Open
netr0m opened this issue Apr 10, 2024 · 0 comments · May be fixed by #62
Open

Broken TLS when TLS_CERT_EMAIL uses an invalid domain name #66

netr0m opened this issue Apr 10, 2024 · 0 comments · May be fixed by #62
Assignees
@netr0m
Labels
🐛 bug Something isn't working

Comments

@netr0m
Copy link
Contributor

netr0m commented Apr 10, 2024

Expected Behaviour

For HTTPS certificates to be acquired and used

Actual Behaviour

Using the .env template's default (noreply-cert@juicesh.op, which is an invalid domain), the certificate acquisiton process fails due to invalid domain

E0410 09:32:12.711413       1 setup.go:271] cert-manager/controller/clusterissuers "msg"="skipping retrying account registration as a BadRequest response was returned from the ACME server" "error"="400 urn:ietf:params:acme:error:invalidContact: Error creating new account :: contact email \"noreply-cert@juicesh.op\" has invalid domain : Domain name does not end with a valid public suffix (TLD)"

Steps to Reproduce
@netr0m netr0m added the 🐛 bug Something isn't working label Apr 10, 2024
@netr0m netr0m self-assigned this Apr 10, 2024
@netr0m netr0m linked a pull request Apr 10, 2024 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@netr0m netr0m

Labels
🐛 bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: automated deployment via Actions bouvet/nord-juice-shop
1 participant
@netr0m