Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is: dev.dynamic-biosensors.com
I ran this docker-compose.yml file:
version: '3'
services:
certbot:
container_name: certbot
image: certbot/certbot:latest
command: >
certonly
--preferred-challenges=dns
--manual-auth-hook /app/authenticator.sh
--manual-cleanup-hook /app/cleanup.sh
--domain ${DOMAIN}
--email ${EMAIL}
--agree-tos
--non-interactive
--manual
-v
volumes:
- ./etc/letsencrypt:/etc/letsencrypt
- ./certbot/data:/var/www/certbot
- ./certbot/logs:/var/log/letsencrypt
- ./scripts/authenticator.sh:/app/authenticator.sh
- ./scripts/cleanup.sh:/app/cleanup.sh
with a .env
file containing
DOMAIN = test000.dev.dynamic-biosensors.com
EMAIL = it@dynamic-biosensors.com
and a two files in the scripts folder:
git@dbs-git01:~/certbot/scripts$ ls -la
total 16
drwxrwxr-x 2 git git 4096 Aug 10 14:50 .
drwxrwxr-x 6 git git 4096 Aug 10 14:50 ..
-rwxrwxr-x 1 git git 1153 Aug 10 14:33 authenticator.sh
-rwxrwxr-x 1 git git 822 Aug 10 14:34 cleanup.sh
It produced this output:
git@dbs-git01:~/certbot$ sudo docker compose up
[+] Running 1/0
✔ Container certbot Recreated 0.0s
Attaching to certbot
certbot | Saving debug log to /var/log/letsencrypt/letsencrypt.log
certbot | Plugins selected: Authenticator manual, Installer None
certbot | Requesting a certificate for test000.dev.dynamic-biosensors.com
certbot | Performing the following challenges:
certbot | dns-01 challenge for test000.dev.dynamic-biosensors.com
certbot | Running manual-auth-hook command: /app/authenticator.sh
certbot | Hook '--manual-auth-hook' for test000.dev.dynamic-biosensors.com reported error code 127
certbot | Hook '--manual-auth-hook' for test000.dev.dynamic-biosensors.com ran with error output:
certbot | /bin/sh: /app/authenticator.sh: not found
certbot | Waiting for verification...
certbot | Challenge failed for domain test000.dev.dynamic-biosensors.com
certbot | dns-01 challenge for test000.dev.dynamic-biosensors.com
certbot |
certbot | Certbot failed to authenticate some domains (authenticator: manual). The Certificate Authority reported these problems:
certbot | Domain: test000.dev.dynamic-biosensors.com
certbot | Type: dns
certbot | Detail: DNS problem: NXDOMAIN looking up TXT for _acme-challenge.test000.dev.dynamic-biosensors.com - check that a DNS record exists for this domain
certbot |
certbot | Hint: The Certificate Authority failed to verify the DNS TXT records created by the --manual-auth-hook. Ensure that this hook is functioning correctly and that it waits a sufficient duration of time for DNS propagation. Refer to "certbot --help manual" and the Certbot User Guide.
certbot |
certbot |
certbot | Cleaning up challenges
certbot | Running manual-cleanup-hook command: /app/cleanup.sh
certbot | Hook '--manual-cleanup-hook' for test000.dev.dynamic-biosensors.com reported error code 127
certbot | Hook '--manual-cleanup-hook' for test000.dev.dynamic-biosensors.com ran with error output:
certbot | /bin/sh: /app/cleanup.sh: not found
certbot | Some challenges have failed.
certbot | 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 exited with code 1
My web server is (include version):
is not reachable from the internet, which is why we are running custom scripts. We know that the scripts work because we were able to receive certificates for the server manually using those scripts.
The operating system my web server runs on is (include version):
Ubuntu 22.04.1 LTS
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
no
The version of my client is (e.g. output of certbot --version
or certbot-auto --version
if you're using Certbot):
certbot:latest (see above)