infinityofspace / certbot_dns_duckdns

Plugin for certbot for a DNS-01 challenge with a DuckDNS domain.
MIT License
75 stars 17 forks source link

[Bug]: how to get wildcard and normal domain cert while using docker-compose #140

Open Dialgatrainer02 opened 6 months ago

Dialgatrainer02 commented 6 months ago

OS info

running in docker latest tag

Docker image

certbot_dns_duckdns version

i cant get this from inside the container as it exist before i can exec into it

certbot version

i cant get this from inside the container as it exist before i can exec into it

Bug description

cant retrive both a wildcard and domain cert using docker-compose

Expected behaviour description

both the doamin ands wild card certs should be in made

Relevant log output

✔ Container certbot_dns_duckdns  Created                                                     0.0s 
Attaching to certbot_dns_duckdns
certbot_dns_duckdns  | Saving debug log to /var/log/letsencrypt/letsencrypt.log
certbot_dns_duckdns  | Account registered.
certbot_dns_duckdns  | Requesting a certificate for ######.duckdns.org and *.########.duckdns.org
certbot_dns_duckdns  | Waiting 30 seconds for DNS changes to propagate
certbot_dns_duckdns  | An unexpected error occurred:
certbot_dns_duckdns  | requests.exceptions.ConnectionError: ('Connection aborted.', RemoteDisconnected('Remote end closed connection without response'))
certbot_dns_duckdns  | Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.
certbot_dns_duckdns exited with code 1

Command

version: "3.9"
services:
  certbot:
    image: "infinityofspace/certbot_dns_duckdns:latest"
    container_name: "certbot_dns_duckdns"
    volumes:
      - "./data/letsencrypt:/etc/letsencrypt"
      - "./data/logs:/var/log/letsencrypt"
    command: certonly
      --non-interactive
      --agree-tos
      --email ########################
      --preferred-challenges dns
      --expand
      --authenticator dns-duckdns
      --dns-duckdns-token #################
      --dns-duckdns-propagation-seconds 30
      -d *.$HOST
      -d $HOST

this gave me the above error i have also tried

version: "3.9"
services:
  certbot:
    image: "infinityofspace/certbot_dns_duckdns:latest"
    container_name: "certbot_dns_duckdns"
    volumes:
      - "./data/letsencrypt:/etc/letsencrypt"
      - "./data/logs:/var/log/letsencrypt"
    command: certonly
      --non-interactive
      --agree-tos
      --email #################################
      --preferred-challenges dns
      --expand
      --authenticator dns-duckdns
      --dns-duckdns-token ###############################
      --dns-duckdns-propagation-seconds 30
      --staging
      -d "*.${HOST}"
  certbot1:
    image: "infinityofspace/certbot_dns_duckdns:latest"
    container_name: "certbot1_dns_duckdns"
    volumes:
      - "./data/letsencrypt:/etc/letsencrypt"
      - "./data/logs:/var/log/letsencrypt"
    command: certonly
      --non-interactive
      --agree-tos
      --email ##############################
      --preferred-challenges dns
      --expand
      --authenticator dns-duckdns
      --dns-duckdns-token ##########################
      --dns-duckdns-propagation-seconds 30
      --staging
      -d "${HOST}"

this also fails as it detecs there another instance running and exists


### DNS records

```shell
how do i get this

Steps to reproduce

run the docker compose file with a valid host from duckdns

Additional context

i have used nginx proxy manager before and it has made wildcard and domain certs is there any alternative way to do this?

Checklist

Dialgatrainer02 commented 6 months ago

apparently what im looking for is a san certificate