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

subdomains do not obtain letsencrypt certificate #12

Open
ivoba opened this issue Jun 28, 2021 · 1 comment
Open

subdomains do not obtain letsencrypt certificate #12

ivoba opened this issue Jun 28, 2021 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@ivoba
Copy link

ivoba commented Jun 28, 2021

Describe the bug
I cant get letsencrypt certificates for subdomains.

To Reproduce
I have the A records of the subdomains pointing to the Server.
In the stack yaml file i added the known subdomains:

traefik.frontend.rule=Host:{{ domains.main }},{{ domains.main_www }},{{ domains.eco_ivobathke }},{{ domains.oxid_ivobathke }}

The letsencrypt block in traefik.yml.j2 is:

{% if letsencrypt %} # you can also use conditional statements
      - --acme
      - --acme.acmeLogging
      - --acme.storage=traefik/acme/account
      - --acme.entryPoint=https
      - --acme.email=admin@{{ domains.main }}
      - --acme.httpchallenge.entrypoint=http
      - --acme.domains={{ domains.main }},{{ domains.main_www }}
{% endif %}

I am reading about defining main & sans domain in the traefik.toml file.
https://doc.traefik.io/traefik/v1.7/configuration/acme/#domains
But i dont see how to use this here, maybe to switch to toml config instead of commands with the traefik image?

Checking the logs i see:

Datastore sync error: object lock value: expected ...

Seems related to: traefik/traefik#3487

Expected behavior
Traefik should automatically request letsencrypt certificates for known subdomains.

@ivoba ivoba added the bug Something isn't working label Jun 28, 2021
@ivoba
Copy link
Author

ivoba commented Jun 29, 2021

Switching to acme.json as store instead of Consul makes at least the main domain obtain a letsencrypt certificate.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants