-
Notifications
You must be signed in to change notification settings - Fork 81
update letsencrypt server URL to prod #465
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
Conversation
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.
thanks for the quick PR
✨ Coder.com for PR #465 deployed! It will be updated on every commit.
|
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.
Do we use staging anywhere else in the docs?
Not that I'm aware of. The other guides actually had the production URL set, so this change will make the guides consistent. Side note: I'm going to push another commit to fix an issue with the |
@@ -104,7 +104,7 @@ To make sure that your `clusterIssuer` can change your DNS settings, | |||
preferredChain: "" | |||
privateKeySecretRef: | |||
name: example-issuer-account-key | |||
server: https://acme-staging-v02.api.letsencrypt.org/directory | |||
server: https://acme-v02.api.letsencrypt.org/directory |
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.
Should we provide examples for both? I imagine that someone would want to test with staging first, and then switch to production once they confirm it works, because I think the rate limits are different between staging and prod?
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.
Correct - the rate limits are different. See here. I'm in favor of including an example for each, so users are aware of both options and can decide for themselves.
making this change to prevent untrusted certs from being used, and providing a sub-optimal TLS config experience for users.