Test for case when challenge_altnames is empty (#321)

[andy/dehydrated.git] / docs / troubleshooting.md

diff --git a/docs/troubleshooting.md b/docs/troubleshooting.md
index d0c79b270d415aebd296ba76250b60b0d84b1225..4823fe96ebef97ec88b64ff9fbd9112676882d05 100644 (file)
--- a/docs/troubleshooting.md
+++ b/docs/troubleshooting.md
@@ -6,17 +6,27 @@ 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 letsencrypt.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.
 
+## "Provided agreement URL [LICENSE1] does not match current agreement URL [LICENSE2]"
+
+Set LICENSE in your config to the value in place of "LICENSE2".
+
+LICENSE1 and LICENSE2 are just placeholders for the real values in this troubleshooting document!
+
 ## "Error creating new cert :: Too many certificates already issued for: [...]"
 
-This is not an issue with letsencrypt.sh but an API limit with letsencrypt.
+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.
 
+## "Certificate request has 123 names, maximum is 100."
+
+This also is an API limit from boulder, you are requesting to sign a certificate with way too many domains.
+
 ## Invalid challenges
 
 There are a few factors that could result in invalid challenges.