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.

Sign up for GitHub

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

is posible to aceppt wildcard for letsencrypt? #2

Closed

quautla opened this issue Mar 4, 2020 · 1 comment

quautla commented Mar 4, 2020

I noticed recently that Letsencrypt accept wildcards, but I don´t know if this version of docker container can be configured via docker-compose.yml like this

    environment:
      - LETSENCRYPT_HOST="*.ctoadmin.mx"
      - [email protected]
      - PORT=8080
      - VIRTUAL_HOST="*.ctoadmin.mx"
    networks:
      - reverse-proxy
    restart: always

instead of:

LETSENCRYPT_HOST=portal1.mydomain.com,portal2.mydomain.com,portal3.mydomain.com
VIRTUAL_HOST=portal1.mydomain.com,portal2.mydomain.com,portal3.mydomain.com

And the second question where could I obtain the value for te TXT record:

Please deploy a DNS TXT record under the name
_acme-challenge.mydomain.com with the following value:
 
kzVNNLb5zvWxxiW30WbdD54OMYO5gbXRmqmpKPHihmQ
 
Before continuing, verify the record is deployed.

The text was updated successfully, but these errors were encountered:

Owner

Alexander-Krause-Glau commented Mar 5, 2020

Hi @quautla, for the first question see:

for the second question see:

How to use Let's Encrypt DNS challenge validation nginx-proxy/acme-companion#358

Alexander-Krause-Glau closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment