Skip to content
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

Docs: ACME Overhaul #3421

Merged
merged 3 commits into from
Jun 5, 2018
Merged

Docs: ACME Overhaul #3421

merged 3 commits into from
Jun 5, 2018

Conversation

dargmuesli
Copy link
Contributor

What does this PR do?

  • Corrects several stylistic inadequacies
  • Orders topics lexicographically
  • Merges the two provider tables into one
  • Fixes some links
  • Removes duplication in multiple occurrences
  • Improves explanation of verification methods and problems

Motivation

The obvious stylistic inadequacies in the ACME docs article.

More

  • Added/updated documentation

Additional Notes

Please have a glance over my updated descriptions of methods and problems and check if they are indeed correct.

@dtomcej
Copy link
Contributor

dtomcej commented Jun 4, 2018

@dargmuesli Can you please rebase this PR off the 1.6 branch instead of master?

Thanks!

@dargmuesli dargmuesli changed the base branch from master to v1.6 June 4, 2018 15:20
@dargmuesli dargmuesli requested review from a team as code owners June 4, 2018 15:24
@dargmuesli
Copy link
Contributor Author

Sure, did so. I hope I solved the merge conflicts corretly ;)

@ldez
Copy link
Contributor

ldez commented Jun 4, 2018

@dargmuesli could you rebase instead merge: git rebase --onto upstream/v1.6 <parent_commit>

@dargmuesli
Copy link
Contributor Author

Oh, sorry. I just followed GitHub's UI there. I guess I can force-push a rebased version?

@ldez ldez changed the base branch from v1.6 to master June 4, 2018 15:32
@ldez
Copy link
Contributor

ldez commented Jun 4, 2018

I reseted your branch.
Now you can rebase git rebase --onto upstream/v1.6 HEAD^
And push force.

@dargmuesli
Copy link
Contributor Author

Sorry once again, I was just really confused which branch did what... I hope everything's correct now?

@ldez ldez changed the base branch from master to v1.6 June 4, 2018 15:54
@ldez ldez removed the bot/no-merge label Jun 4, 2018

See also [Let's Encrypt examples](/user-guide/examples/#lets-encrypt-support) and [Docker & Let's Encrypt user guide](/user-guide/docker-and-lets-encrypt).
See [Let's Encrypt examples](/user-guide/examples/#lets-encrypt-support) and [Docker & Let's Encrypt user guide](/user-guide/docker-and-lets-encrypt) too.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I personally prefer as well to too

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good idea :)

# - Uncomment the line to run on the staging let's encrypt server.
# - Leave comment to go to prod.
# Uncomment the line to use Let's Encrypt's staging server,
# leave comment to go to prod.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

leave commented to go to prod

#
# Optional
#
# [acme.dnsChallenge]

# Provider used.
# DNS management provider used.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

not sure management is needed here

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah well, it's arguably unnecessary.

#
# Required
#
# provider = "digitalocean"

# By default, the provider will verify the TXT DNS challenge record before letting ACME verify.
# If delayBeforeCheck is greater than zero, avoid this & instead just wait so many seconds.
# If delayBeforeCheck is greater than zero, this is avoided and the given duration in seconds is waited.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If delayBeforeCheck is greater than zero, this check is delayed for the configured duration in seconds.

- a JSON file,
- a KV store entry.
By default, the `provider` will verify the TXT DNS challenge record before letting ACME verify.
If `delayBeforeCheck` is greater than zero, this is avoided and the given duration in seconds is waited.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

same as above


!!! note
It's possible to store up to approximately 100 ACME certificates in Consul.
It is impossible possible to define a wildcard on a wildcard domain (for example `*.*.local.com`).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It is not possible to request a double wildcard certificate for a domain (for example ..local.com)

!!! note
It's possible to store up to approximately 100 ACME certificates in Consul.
It is impossible possible to define a wildcard on a wildcard domain (for example `*.*.local.com`).
Due to ACME limitation it is neither possible to define wildcards in SANs (alternative domains). Thus, the wildcard domain has to be defined as a main domain.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

it is not possible

All DNS providers allow creating ACME wildcard certificates.
However, many troubles can appear for wildcard domains with SANs.
!!! note
When Træfik is launched in a container the storage file's parent directory needs to be mounted to be able to access the backup file on the host.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

launched in a container, the storage


For example : if `acme.storage` value is `/etc/traefik/acme/acme.json`, the backup file will be named `/etc/traefik/acme/acme.json.bak`.
1. ACME certificates already generated before downtime
1. Expired ACME certificates
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should this be 2. etc?

Copy link
Contributor Author

@dargmuesli dargmuesli Jun 4, 2018

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be interpreted as 2. by markdown renderers (GitHub does that). This way one can easily add a new list element without the need to increment all following.


!!! note
When Træfik is launched in a container, do not forget to create a volume of the parent folder to get the backup file on the host.
Otherwise, the backup file will be permanently deleted when the container is stopped, and Træfik will not be able to generate it again.
For new (sub)domains which need Let's Encrypt authentification the default Træfik certificate will be used until Træfik is restarted.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

which need Let's Encrypt certificates generated, the default

Copy link
Contributor

@dtomcej dtomcej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM
:shipit:

Copy link
Member

@juliens juliens left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link
Contributor

@ldez ldez left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

dargmuesli and others added 3 commits June 5, 2018 08:32
~ Corrected several stylistic inadequacies
~ Ordered topics lexicographically
~ Merged the two provider tables into one
~ Fixed some links
~ Removed duplication in multiple occurrences
~ Implements requested changes by @dtomcej
@dargmuesli
Copy link
Contributor Author

Nice, thank you guys!

@dargmuesli dargmuesli deleted the docs_acme branch March 20, 2019 04:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants