starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-03-22 00:59:04 +01:00
Code Issues 79 Packages Projects Releases 10 Wiki Activity

fixed a few things after project rename

Browse Source
This commit is contained in:
Lukas Schauer
2016-09-13 19:57:14 +02:00
parent 0ae567aced
commit ec49a4433b
9 changed files with 24 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/troubleshooting.md
View File

@@ -6,7 +6,7 @@ Generally if the following information doesn't provide a solution to your proble
You probably changed from staging-CA to production-CA (or the other way).
Currently dehydrated.sh doesn't detect a missing registration on the selected CA,
Currently dehydrated doesn't detect a missing registration on the selected CA,
the current workaround is to move `private_key.pem` (and, if you care, `private_key.json`) out of the way so the scripts generates and registers a new one.
This will hopefully be fixed in the future.
@@ -19,7 +19,7 @@ LICENSE1 and LICENSE2 are just placeholders for the real values in this troubles
## "Error creating new cert :: Too many certificates already issued for: [...]"
This is not an issue with dehydrated.sh but an API limit with boulder (the ACME server).
This is not an issue with dehydrated but an API limit with boulder (the ACME server).
At the time of writing this you can only create 5 certificates per domain in a sliding window of 7 days.