starred/dehydrated
1
0
Fork 0
mirror of https://github.com/dehydrated-io/dehydrated.git synced 2026-05-07 07:33:26 +02: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

2
docs/domains_txt.md
View File

@@ -1,6 +1,6 @@
### domains.txt
dehydrated.sh uses the file `domains.txt` as configuration for which certificates should be requested.
dehydrated uses the file `domains.txt` as configuration for which certificates should be requested.
The file should have the following format:

2
docs/examples/config
View File

@@ -1,5 +1,5 @@
########################################################
# This is the main config file for dehydrated.sh #
# This is the main config file for dehydrated #
# #
# This file is looked for in the following locations: #
# $SCRIPTDIR/config (next to this script) #

2
docs/per-certificate-config.md
View File

@@ -1,6 +1,6 @@
# Config on per-certificate base
dehydrated.sh allows a few configuration variables to be set on a per-certificate base.
dehydrated allows a few configuration variables to be set on a per-certificate base.
To use this feature create a `config` file in the certificates output directory (e.g. `certs/example.org/config`).

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.

2
docs/wellknown.md
View File

@@ -5,7 +5,7 @@ It will do that for any (sub-)domain you want to sign a certificate for.
At the moment you'll need to have that location available over normal HTTP on port 80 (redirect to HTTPS will work, but starting point is always HTTP!).
dehydrated.sh has a config variable called `WELLKNOWN`, which corresponds to the directory which should be served under `/.well-known/acme-challenge` on your domain. So in the above example the token would have been saved as `$WELLKNOWN/m4g1C-t0k3n`.
dehydrated has a config variable called `WELLKNOWN`, which corresponds to the directory which should be served under `/.well-known/acme-challenge` on your domain. So in the above example the token would have been saved as `$WELLKNOWN/m4g1C-t0k3n`.
If you only have one docroot on your server you could easily do something like `WELLKNOWN=/var/www/.well-known/acme-challenge`, for anything else look at the example below.