# LetsEncrypt Docker Issue **URL:** \ **Category:** Help\ **Created:** [April 29, 2020, 12:48pm UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109 "2020-04-29T12:48:45Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![letsencryptprakash](https://avatars.discourse-cdn.com/v4/letter/l/f07891/32.png) [@letsencryptprakash](https://community.letsencrypt.org/u/letsencryptprakash)\ **Post date:** [April 29, 2020, 12:48pm UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/1 "2020-04-29T12:48:45Z")
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. [https://crt.sh/?q=example.com](https://crt.sh/?q=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: [stldintux02.sial.com](http://stldintux02.sial.com) I ran this command: ```auto sudo docker run -it --rm \ -v /docker-volumes/etc/letsencrypt:/etc/letsencrypt \ -v /docker-volumes/var/lib/letsencrypt:/var/lib/letsencrypt \ -v /docker/letsencrypt-docker-nginx/src/letsencrypt/letsencrypt-site:/data/letsencrypt \ -v "/docker-volumes/var/log/letsencrypt:/var/log/letsencrypt" \ certbot/certbot \ certonly --webroot \ --register-unsafely-without-email --agree-tos \ --webroot-path=/data/letsencrypt \ --staging \ -d stldintux02.sial.com -d www.stldintux02.sial.com ``` It produced this output: ### Requesting Let’s Encrypt certificate for [stldintux02.sial.com](http://stldintux02.sial.com) … Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for [stldintux02.sial.com](http://stldintux02.sial.com) http-01 challenge for [www.stldintux02.sial.com](http://www.stldintux02.sial.com) Using the webroot path /var/www/certbot for all unmatched domains. Waiting for verification… Challenge failed for domain [stldintux02.sial.com](http://stldintux02.sial.com) Challenge failed for domain [www.stldintux02.sial.com](http://www.stldintux02.sial.com) http-01 challenge for [stldintux02.sial.com](http://stldintux02.sial.com) http-01 challenge for [www.stldintux02.sial.com](http://www.stldintux02.sial.com) Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: ### Reloading nginx … My web server is (include version): I am using Docker Nginx The operating system my web server runs on is (include version): Linux [stldintux02.sial.com](http://stldintux02.sial.com) 3.10.0-957.1.3.el7.x86\_64 #1 SMP Thu Nov 29 14:49:43 UTC 2018 x86\_64 x86\_64 x86\_64 GNU/Linux 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): Docker images (certbot/certbot) ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [April 29, 2020, 12:57pm UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/2 "2020-04-29T12:57:42Z")
Hi @letsencryptprakash > [@letsencryptprakash](#): > > Domain: [stldintux02.sial.com](http://stldintux02.sial.com) > Type: dns > Detail: DNS problem: NXDOMAIN looking up A for [stldintux02.sial.com](http://stldintux02.sial.com) > > - check that a DNS record exists for this domain > > Domain: [www.stldintux02.sial.com](http://www.stldintux02.sial.com) > Type: dns > Detail: DNS problem: NXDOMAIN looking up A for > [www.stldintux02.sial.com](http://www.stldintux02.sial.com) - check that a DNS record exists for this > domain there is a check of your domain, ~~ one hour old - [https://check-your-website.server-daten.de/?q=stldintux02.sial.com](https://check-your-website.server-daten.de/?q=stldintux02.sial.com) - same result: | Host | T | IP-Address | is auth. | ∑ Queries | ∑ Timeout | | --- | --- | --- | --- | --- | --- | | [stldintux02.sial.com](http://stldintux02.sial.com) | | Name Error | yes | 1 | 0 | | [www.stldintux02.sial.com](http://www.stldintux02.sial.com) | | Name Error | yes | 1 | 0 | There is no A or AAAA record defined. Are you the owner of that domain? If yes, create an A record or use dns validation. If no, you can't create a certificate with that domain name. ---
**Author:** ![letsencryptprakash](https://avatars.discourse-cdn.com/v4/letter/l/f07891/32.png) [@letsencryptprakash](https://community.letsencrypt.org/u/letsencryptprakash)\ **Post date:** [April 29, 2020, 2:03pm UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/3 "2020-04-29T14:03:03Z")
@JuergenAuer Could you please advise me how to create the A record ---
**Author:** ![letsencryptprakash](https://avatars.discourse-cdn.com/v4/letter/l/f07891/32.png) [@letsencryptprakash](https://community.letsencrypt.org/u/letsencryptprakash)\ **Post date:** [April 30, 2020, 3:38am UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/4 "2020-04-30T03:38:44Z")
@JuergenAuer we are already having the record for this, please check below [stldintux02.sial.com](http://stldintux02.sial.com) Server: [stladdc01.global.sial.com](http://stladdc01.global.sial.com) Address: 141.247.239.48 Name: [stldintux02.sial.com](http://stldintux02.sial.com) Address: 141.247.199.236 > 141.247.199.236 > Server: [stladdc01.global.sial.com](http://stladdc01.global.sial.com) > Address: 141.247.239.48 Name: [stldintux02.sial.com](http://stldintux02.sial.com) Address: 141.247.199.236 -bash-4.2$ dig [stldintux02.sial.com](http://stldintux02.sial.com) ; \<\<\>\> DiG 9.9.4-RedHat-9.9.4-72.el7 \<\<\>\> [stldintux02.sial.com](http://stldintux02.sial.com) ;; global options: +cmd ;; Got answer: ;; -\>\>HEADER\<\<- opcode: QUERY, status: NOERROR, id: 17834 ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;[stldintux02.sial.com](http://stldintux02.sial.com). IN A ;; ANSWER SECTION: [stldintux02.sial.com](http://stldintux02.sial.com). 28800 IN A 141.247.199.236 ;; Query time: 1 msec ;; SERVER: 141.247.9.18#53(141.247.9.18) ;; WHEN: Wed Apr 29 22:37:55 CDT 2020 ;; MSG SIZE rcvd: 65 Please let me know is there anything else i need to add, if so could you please advise me how to add the where to add. Thanks ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [April 30, 2020, 6:15am UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/5 "2020-04-30T06:15:59Z")
> [@letsencryptprakash](#): > > we are already having the record for this, please check below Read the output of your check - [https://check-your-website.server-daten.de/?q=stldintux02.sial.com](https://check-your-website.server-daten.de/?q=stldintux02.sial.com) `ns01.brandshelter.com` is the name server of [sial.com](http://sial.com), there you have to create the A record. There is nothing - same result: | Host | T | IP-Address | is auth. | ∑ Queries | ∑ Timeout | | --- | --- | --- | --- | --- | --- | | [stldintux02.sial.com](http://stldintux02.sial.com) | | Name Error | yes | 1 | 0 | | [www.stldintux02.sial.com](http://www.stldintux02.sial.com) | | Name Error | yes | 1 | 0 | ---
**Author:** ![letsencryptprakash](https://avatars.discourse-cdn.com/v4/letter/l/f07891/32.png) [@letsencryptprakash](https://community.letsencrypt.org/u/letsencryptprakash)\ **Post date:** [May 6, 2020, 9:05am UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/6 "2020-05-06T09:05:56Z")
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. [https://crt.sh/?q=example.com](https://crt.sh/?q=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: [stldintux02.sial.com](http://stldintux02.sial.com) I ran this command: sudo docker run -it --rm -v /docker-volumes/etc/letsencrypt:/etc/letsencrypt -v /docker-volumes/var/lib/letsencrypt:/var/lib/letsencrypt -v /docker/letsencrypt-docker-nginx/src/letsencrypt/letsencrypt-site:/data/letsencrypt -v “/docker-volumes/var/log/letsencrypt:/var/log/letsencrypt” certbot/certbot certonly --webroot –register-unsafely-without-email --agree-tos –webroot-path=/data/letsencrypt –staging -d [stldintux02.sial.com](http://stldintux02.sial.com) -d [www.stldintux02.sial.com](http://www.stldintux02.sial.com) It produced this output: ### Requesting Let’s Encrypt certificate for [stldintux02.sial.com](http://stldintux02.sial.com/) … Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for [stldintux02.sial.com](http://stldintux02.sial.com/) http-01 challenge for [www.stldintux02.sial.com](http://www.stldintux02.sial.com/) Using the webroot path /var/www/certbot for all unmatched domains. Waiting for verification… Challenge failed for domain [stldintux02.sial.com](http://stldintux02.sial.com/) Challenge failed for domain [www.stldintux02.sial.com](http://www.stldintux02.sial.com/) http-01 challenge for [stldintux02.sial.com](http://stldintux02.sial.com/) http-01 challenge for [www.stldintux02.sial.com](http://www.stldintux02.sial.com/) Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server:Domain: [stldintux02.sial.com](http://stldintux02.sial.com/) Type: dns Detail: DNS problem: NXDOMAIN looking up A for [stldintux02.sial.com](http://stldintux02.sial.com/) - check that a DNS record exists for this domainDomain: [www.stldintux02.sial.com](http://www.stldintux02.sial.com/) Type: dns Detail: DNS problem: NXDOMAIN looking up A for [www.stldintux02.sial.com](http://www.stldintux02.sial.com/) - check that a DNS record exists for this domain My web server is (include version): The operating system my web server runs on is (include version): My hosting provider, if applicable, is: I can login to a root shell on my machine (yes or no, or I don’t know): I’m using a control panel to manage my site (no, or provide the name and version of the control panel): The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you’re using Certbot): Hello LetsEncrypt, [stldintux02.sial.com](http://stldintux02.sial.com) this is my internal servers and i want to generate the Certificate for this, could some one please help me to generate the certificate on this. Thanks ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [May 6, 2020, 9:47am UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/7 "2020-05-06T09:47:05Z")
If it isn’t possible that you create a public visible A-record, you can’t use http validation. Switch to dns validation. > **[Challenge Types - Let's Encrypt - Free SSL/TLS Certificates](https://letsencrypt.org/docs/challenge-types/)** > > Last updated: Feb 24, 2020 | See all Documentation When you get a certificate from Let’s Encrypt, our servers validate that you control the domain names in that certificate using “challenges,” as defined by the ACME standard. Most of the time, this... ---
**Author:** ![letsencryptprakash](https://avatars.discourse-cdn.com/v4/letter/l/f07891/32.png) [@letsencryptprakash](https://community.letsencrypt.org/u/letsencryptprakash)\ **Post date:** [May 6, 2020, 11:12am UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/8 "2020-05-06T11:12:12Z")
@JuergenAuer : I have used below command and again getting error sudo certbot -d [stldintux02.sial.com](http://stldintux02.sial.com) --manual --preferred-challenges dns certonly * * * Please deploy a DNS TXT record under the name \_acme-challenge.stldintux02.sial.com with the following value: 2mPXbYZpl0i2ucwnPx2SKz6q58BpikTRRI4WlA6pT0s Before continuing, verify the record is deployed. * * * Press Enter to Continue Waiting for verification… Challenge failed for domain [stldintux02.sial.com](http://stldintux02.sial.com) dns-01 challenge for [stldintux02.sial.com](http://stldintux02.sial.com) Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: Could you please advise how to resolve this issue ---
**Author:** ![letsencryptprakash](https://avatars.discourse-cdn.com/v4/letter/l/f07891/32.png) [@letsencryptprakash](https://community.letsencrypt.org/u/letsencryptprakash)\ **Post date:** [May 8, 2020, 12:23pm UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/9 "2020-05-08T12:23:16Z")
@JuergenAuer : I tried with DNS validation but still i am getting the below error, could you please advise on this. sudo certbot -d [stldintux02.sial.com](http://stldintux02.sial.com) --server [https://acme-v02.api.letsencrypt.org/directory](https://acme-v02.api.letsencrypt.org/directory) --manual --preferred-challenges dns certonly Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator manual, Installer None Starting new HTTPS connection (1): [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org) Obtaining a new certificate Performing the following challenges: dns-01 challenge for [stldintux02.sial.com](http://stldintux02.sial.com) * * * NOTE: The IP of this machine will be publicly logged as having requested this certificate. If you’re running certbot in manual mode on a machine that is not your server, please ensure you’re okay with that. Are you OK with your IP being logged? * * * (Y)es/(N)o: y * * * Please deploy a DNS TXT record under the name \_acme-challenge.stldintux02.sial.com with the following value: wPbvV221u41kEKYTvdiMQCqqACq3aSpxbjJTe9zNTY4 Before continuing, verify the record is deployed. * * * Press Enter to Continue Waiting for verification… Challenge failed for domain [stldintux02.sial.com](http://stldintux02.sial.com) dns-01 challenge for [stldintux02.sial.com](http://stldintux02.sial.com) Cleaning up challenges Some challenges have failed. IMPORTANT NOTES: - The following errors were reported by the server: ---
**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\ **Post date:** [May 8, 2020, 12:30pm UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/10 "2020-05-08T12:30:27Z")
> [@letsencryptprakash](#): > > I tried with DNS validation but still i am getting the below error, could you please advise on this. Use the online tool after creating the TXT record. There are some errors possible, the tool checks that. Checking these things manual is terrible. ---
**Author:** ![letsencryptprakash](https://avatars.discourse-cdn.com/v4/letter/l/f07891/32.png) [@letsencryptprakash](https://community.letsencrypt.org/u/letsencryptprakash)\ **Post date:** [May 8, 2020, 1:45pm UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/11 "2020-05-08T13:45:49Z")
@JuergenAuer : Is there any options to change the DNS lookup server name other than default, because its looking for default server and getting the error as failed. -bash-4.2$ nslookup [stldintux02.sial.com](http://stldintux02.sial.com) Server: 141.247.9.18 ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [June 7, 2020, 1:45pm UTC](https://community.letsencrypt.org/t/letsencrypt-docker-issue/121109/12 "2020-06-07T13:45:51Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.