The verification procedure in my previous post resulted in the following messages fo one website:
Press Enter to Continue
Waiting for verification...
←[31mChallenge failed for domain www.smackdabit.com←[0m
←[31mChallenge failed for domain smackdabit.com←[0m
←[31mChallenge failed for domain smackdabit.net←[0m
←[31mChallenge failed for domain smackdabit.org←[0m
←[31mChallenge failed for domain www.smackdabit.net←[0m
←[31mChallenge failed for domain www.smackdabit.org←[0m
http-01 challenge for www.smackdabit.com
http-01 challenge for smackdabit.com
http-01 challenge for smackdabit.net
http-01 challenge for smackdabit.org
http-01 challenge for www.smackdabit.net
http-01 challenge for www.smackdabit.org
Cleaning up challenges
←[31mSome challenges have failed.←[0m
←[1m
IMPORTANT NOTES:
←[0m - The following errors were reported by the server:
Domain: smackdabit.com
Type: connection
Detail: Fetching https://www.smackdabit.com/index.php: Timeout
during connect (likely firewall problem)
Domain: smackdabit.net
Type: connection
Detail: Fetching
http://smackdabit.net/.well-known/acme-challenge/BXZoVt2SXpW_60e02bWyMUoYTcsV5ZOcQ-kHjLF3m48:
Timeout during connect (likely firewall problem)
Domain: smackdabit.org
Type: connection
Detail: Fetching
http://smackdabit.org/.well-known/acme-challenge/u9ZOdFohruR48iFcNvEx9X-TUoEc52r6U8ENW3ji6JA:
Timeout during connect (likely firewall problem)
Domain: www.smackdabit.net
Type: connection
Detail: Fetching
http://www.smackdabit.net/.well-known/acme-challenge/9gBpeCgZ82XpTnhU0FOMqE4NtyOnY-VmysmmjbWo8lI:
Timeout during connect (likely firewall problem)
Domain: www.smackdabit.org
Type: connection
Detail: Fetching
http://www.smackdabit.org/.well-known/acme-challenge/MAtP77HUl4P04AHwxgbmbLsaPCddE1cA7QJ50peTMxc:
Timeout during connect (likely firewall problem)
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address. Additionally, please check that
your computer has a publicly routable IP address and that no
firewalls are preventing the server from communicating with the
client. If you're using the webroot plugin, you should also verify
that you are serving files from the webroot path you provided.
- The following errors were reported by the server:
Domain: www.smackdabit.com
Type: unauthorized
Detail: Invalid response from https://www.smackdabit.com/index.php
[160.153.32.232]: "<!DOCTYPE html>\n<html lang=\"en\" dir=\"ltr\"
prefix=\"content: http://purl.org/rss/1.0/modules/content/ dc:
http://purl.org/dc/term"
To fix these errors, please make sure that your domain name was
entered correctly and the DNS A/AAAA record(s) for that domain
contain(s) the right IP address.
The domains in question were listed in a previously used batch file. Obviously they weren't entered incorrectly, and there is no firewall that I have any control over. I could not find a solution, but I found another procedure involving adding a TXT record to the domain's DNS record. I modified my batch file to be:
"certbot certonly --manual -d smackdabit.com -d www.smackdabit.com -d smackdabit.org -d www.smackdabit.org -d smackdabit.net -d www.smackdabit.net"
This worked well for the non-www versions, but I was presented with the following errors:
←[0m - The following errors were reported by the server:
Domain: www.smackdabit.com
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.www.smackdabit.com - check that a DNS record exists
for this domain
Domain: www.smackdabit.net
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.www.smackdabit.net - check that a DNS record exists
for this domain
Domain: www.smackdabit.org
Type: dns
Detail: DNS problem: NXDOMAIN looking up TXT for
_acme-challenge.www.smackdabit.org - check that a DNS record exists
for this domain
The domain exists and there is a CNAME entry pointing to www for each of the domains. After some more research I found a suggestion to use an A record instead. Without removing the CNAME entry, I tried to create an A record. GoDaddy's DNS editor would not allow me to create the A record, probably to avoid conflict with the CNAME record.
Further research did not turn anything up, but after some poking around, I made a discovery. Adding ".www" to the "acme-challenge" hostname in the TXT record allowed the domain to be found and ownership to be verified.
The hostname for the TXT record is now "_acme-challenge.www", and verification is complete.