Not creating a certificate for a subdomain

[Rektalizer]

init-letsencrypt.sh works perfectly for domains like website.com or www.website.com, however when specific subdomains required like forum.website.com it fails with this error

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: forum.website.com
  Type:   connection
  Detail: 104.199.106.75: Fetching http://forum.website.com/.well-known/acme-challenge/Y95bRZ3zcitpwUbAA4FAAmB18od-fepB8_vQfBhk_zA: Connection refused

Seems like this is a common issue as there are few of them here. Does any bypass or fix for this exist?

[DavidKaub]

I also have this issue. Is there a workaround?

[soreana]

@DavidKaub @Rektalizer
I just generated a certificate for a subdomain successfully. Have you replaced all the example.org to the subdomain name?

[pmeaney]

If you run into this problem--
Check the certbot container logs.

docker exec -it certbotContainerName sh
cat /var/log/letsencrypt/letsencrypt.log

Scroll up through the logs a bit...
You may see this, as I did-- because I forgot to add a DNS record for the subdomain, via your hosting provider:

Certbot failed to authenticate some domains (authenticator: webroot). The Certificate Authority reported these problems:
  Domain: api.livestauction.com
  Type:   dns
  Detail: DNS problem: NXDOMAIN looking up A for api.livestauction.com - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for api.livestauction.com - check that a DNS record exists for this domain