-
Notifications
You must be signed in to change notification settings - Fork 136
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
replace server urls with v2 urls #196
Comments
Hi @hboetes Why modify the default value of $config does not meet your needs ? |
The code should use sane defaults and in this case use the working server URL, not the outdated one. Your proposal would force all users of the module to fix that problem for themselves whereas the maintainer can fix the problem for everyone. |
With reading those sources I agree we should be defaulting to v2. I also wonder why we even set a default rather than relying on the hardcoded defaults. Probably because we use |
@ekohl I can imagine setting staging as the default, since I’ve never managed to get a cert in one go and use the production one as the non-default, with a switch like: |
Please replace the server URLs with:
https://acme-v02.api.letsencrypt.org/directory
And
https://acme-staging-v02.api.letsencrypt.org/directory
See also:
https://community.letsencrypt.org/t/staging-endpoint-for-acme-v2/49605
https://community.letsencrypt.org/t/acme-v2-production-environment-wildcards/55578
The text was updated successfully, but these errors were encountered: