mirror of
https://github.com/dehydrated-io/dehydrated.git
synced 2026-01-11 22:30:44 +01:00
Default to staging to avoid rate limiting #25
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @reetp on GitHub (Jan 6, 2016).
Without realising (what you mean RTFM?!) I hit the limit quite quickly
It would help to document this fact and use the staging server by default to test.
@lukas2511 commented on GitHub (Jan 8, 2016):
I want this thing to kinda work out-of-the-box, and changing it to staging would probably confuse a lot of users why their new certificates are not working (anymore), so i will not do that. Sorry.
@reetp commented on GitHub (Jan 8, 2016):
Can you modify the readme to make it much clearer then ?
It may save a few people a lot of problems !
@nikku commented on GitHub (Jan 8, 2016):
@reetp Just provide a PR for anything that may help people circumvent this.
@aral commented on GitHub (Feb 12, 2016):
Agree that default should be live but that we should warn regarding rate limit and show how to use the staging server (it’s not even mentioned at the moment and people have to hunt down the URL separately). I’ve just updated the readme with that info and added a pull request: https://github.com/lukas2511/letsencrypt.sh/pull/135 — hope it helps :)
@reetp commented on GitHub (Feb 14, 2016):
Nice thanks !
It is easily overlooked when you are staring to play.
@theibel commented on GitHub (Feb 19, 2019):
"# Path to certificate authority (default: https://acme-v02.api.letsencrypt.org/directory)"
#CA="https://acme-v02.api.letsencrypt.org/directory"
Add this to the main config file:
"# Path to staging certificate authority for testing - run this first (default: none)"
CA="https://acme-staging-v02.api.letsencrypt.org/directory"
When you're done testing, you can simply remove the staging files from your ${BASEDIR}, comment out the staging, and uncomment the live CA. As it is today, each repo (live or staging) has it's own account validation. I've had success running this across several WordPress multisite setups.