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

acme.json always at root #5360

Closed
1 of 2 tasks
trajano opened this issue Sep 12, 2019 · 8 comments
Closed
1 of 2 tasks

acme.json always at root #5360

trajano opened this issue Sep 12, 2019 · 8 comments
Projects
Milestone

Comments

@trajano
Copy link

trajano commented Sep 12, 2019

Do you want to request a feature or report a bug?

Bug

Did you try using a 1.7.x configuration for the version 2.0?

  • Yes
  • No

What did you do?

I got LetsEncrypt working now, but I noticed something was off in that when I restart the server it appears to recreate the certificate again. The commands I am using to configure traefik are:

  - --certificatesresolvers.default.acme.httpchallenge.entrypoint=http
  - --certificatesResolvers.default.acme.email=support@trajano.net
  - --certificatesResolvers.default.acme.storage=/letsencrypt/acme.json

I have this volumes block on the service

volumes:
  - letsencrypt:/letsencrypt

To correspond to the following in the top level compose file:

volumes:
  letsencrypt:

I see the volume when I do docker volume ls but when I try to view it's contents it is empty using this command

docker run -it -v edge_letsencrypt:/mnt bash ls -la //mnt

What did you expect to see?

acme.json present

What did you see instead?

/mnt was empty

Output of traefik version: (What version of Traefik are you using?)

$ docker run traefik:v2.0.0-rc3 version
Version:      2.0.0-rc3
Codename:     montdor
Go version:   go1.13
Built:        2019-09-10T17:10:04Z
OS/Arch:      linux/amd64

What is your environment & configuration (arguments, toml, provider, platform, ...)?

# (paste your configuration here)

If applicable, please paste the log output in DEBUG level (--log.level=DEBUG switch)

(paste your output here)

I also tried to see what's inside the overlay2 folders to peek into the details

/host/var/lib/docker/overlay2 # find . -name "acme.json"
./4f82ac74bd8b3d0fe4de3aafb5a54cc93707219a0677edf22df0180be2d579c7/diff/acme.json
./4f82ac74bd8b3d0fe4de3aafb5a54cc93707219a0677edf22df0180be2d579c7/merged/acme.json
/host/var/lib/docker/overlay2 # 

The files are there and are not empty (they actually contain the proper data)

@traefiker
Copy link
Contributor

Hi! I'm Træfiker 🤖 the bot in charge of communication regulation.

Thanks for your interest in Traefik!

We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.

To confirm this, please join our Community Forum and reach out to us on the Traefik section.

In case I'm wrong (well, that would be embarrassing 😅), my developers will re-open the issue and fix me!

In the meantime, you can double check Traefik's documentation.

@trajano
Copy link
Author

trajano commented Sep 16, 2019

@trajano
Copy link
Author

trajano commented Sep 19, 2019

Issue is still persisting after the 2,0.0 release

@ldez ldez added area/acme kind/bug/possible a possible bug that needs analysis before it is confirmed or fixed. and removed kind/question a question labels Sep 19, 2019
@ldez ldez reopened this Sep 19, 2019
@ldez ldez added this to To do in v2 via automation Sep 19, 2019
@trajano
Copy link
Author

trajano commented Sep 19, 2019

The problem is in the CLI configuration, environment variable configuration works

  TRAEFIK_CERTIFICATESRESOLVERS_DEFAULT_ACME_EMAIL: support@trajano.net
  TRAEFIK_CERTIFICATESRESOLVERS_DEFAULT_ACME_HTTPCHALLENGE_ENTRYPOINT: http
  TRAEFIK_CERTIFICATESRESOLVERS_DEFAULT_ACME_STORAGE: /etc/traefik/acme/default.json

@ldez ldez added kind/bug/confirmed a confirmed bug (reproducible). priority/P1 need to be fixed in next release and removed kind/bug/possible a possible bug that needs analysis before it is confirmed or fixed. priority/P1 need to be fixed in next release labels Sep 19, 2019
@ldez
Copy link
Member

ldez commented Sep 19, 2019

It's just a problem related to case:

  - --certificatesresolvers.default.acme.httpchallenge.entrypoint=http
  - --certificatesResolvers.default.acme.email=support@trajano.net
  - --certificatesResolvers.default.acme.storage=/letsencrypt/acme.json

certificatesresolvers vs certificatesResolvers => you need to use the same case

  - --certificatesresolvers.default.acme.httpchallenge.entrypoint=http
  - --certificatesresolvers.default.acme.email=support@trajano.net
  - --certificatesresolvers.default.acme.storage=/letsencrypt/acme.json

or

  - --certificatesResolvers.default.acme.httpchallenge.entrypoint=http
  - --certificatesResolvers.default.acme.email=support@trajano.net
  - --certificatesResolvers.default.acme.storage=/letsencrypt/acme.json

@ldez ldez added kind/question a question and removed kind/bug/confirmed a confirmed bug (reproducible). labels Sep 19, 2019
@trajano
Copy link
Author

trajano commented Sep 20, 2019

it would be nice to have an error message that says it or at least make sure the documentation pages were consistent on this one. II think I copied from two different pages and eventually got the issue.

@ldez ldez added kind/bug/confirmed a confirmed bug (reproducible). and removed kind/question a question labels Sep 20, 2019
@ldez
Copy link
Member

ldez commented Sep 20, 2019

In the next path release, the problem will be fixed: #5438

The case will no longer need to be consistent.

@traefiker traefiker added this to the 2.0 milestone Sep 20, 2019
@traefiker
Copy link
Contributor

Closed by #5438.

v2 automation moved this from To do to Done Sep 20, 2019
@traefik traefik locked and limited conversation to collaborators Oct 21, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
No open projects
v2
Done
Development

No branches or pull requests

3 participants