# SSl Certificat Problem

**URL:** <https://community.letsencrypt.org/t/ssl-certificat-problem/169468>\
**Category:** Help\
**Created:** [January 11, 2022, 9:49am UTC](https://community.letsencrypt.org/t/ssl-certificat-problem/169468 "2022-01-11T09:49:09Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![ChristianPudenz](https://avatars.discourse-cdn.com/v4/letter/c/3da27b/32.png) [@ChristianPudenz](https://community.letsencrypt.org/u/ChristianPudenz)\
**Post date:** [January 11, 2022, 9:49am UTC](https://community.letsencrypt.org/t/ssl-certificat-problem/169468/1 "2022-01-11T09:49:09Z")

</div>

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](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: [www.thehomeofmyown.com](http://www.thehomeofmyown.com)

I ran this command: certbot --nginx --redirect -d [www.thehomeofmyown.com](http://www.thehomeofmyown.com) -d [thehomeofmyown.com](http://thehomeofmyown.com) -m [admin@thehomeofmyown.com](mailto:admin@thehomeofmyown.com) --agree-tos --no-eff-email

It produced this output: Last login: Mon Jan 10 21:51:16 on console  
christianpudenz@MacBook-Air-von-Christian ~ % ssh [root@104.207.130.242](mailto:root@104.207.130.242)  
[root@104.207.130.242](mailto:root@104.207.130.242)'s password:  
Welcome to Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-84-generic x86\_64)

- Documentation: [https://help.ubuntu.com](https://help.ubuntu.com)
- Management: [https://landscape.canonical.com](https://landscape.canonical.com)
- Support: [Ubuntu Advantage for Infrastructure | Ubuntu](https://ubuntu.com/advantage)

System information as of Tue 11 Jan 2022 09:39:01 AM UTC

System load: 0.0 Processes: 162  
Usage of /: 7.6% of 51.57GB Users logged in: 0  
Memory usage: 29% IPv4 address for enp1s0: 104.207.130.242  
Swap usage: 0%

- Super-optimized for small spaces - read how we shrank the memory  
footprint of MicroK8s to make it the smallest full K8s around.

151 updates can be applied immediately.  
59 of these updates are standard security updates.  
To see these additional updates run: apt list --upgradable

Web console: [https://thehomeofmyown.com:9090/](https://thehomeofmyown.com:9090/) or [https://104.207.130.242:9090/](https://104.207.130.242:9090/)

Last login: Mon Jan 10 14:33:03 2022 from 213.174.20.240  
root@thehomeofmyown:~# certbot --nginx --redirect -d [www.thehomeofmyown.com](http://www.thehomeofmyown.com) -d [thehomeofmyown.com](http://thehomeofmyown.com) -m [admin@thehomeofmyown.com](mailto:admin@thehomeofmyown.com) --agree-tos --no-eff-email  
Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Requesting a certificate for [www.thehomeofmyown.com](http://www.thehomeofmyown.com) and [thehomeofmyown.com](http://thehomeofmyown.com)

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:  
Domain: [www.thehomeofmyown.com](http://www.thehomeofmyown.com)  
Type: dns  
Detail: DNS problem: NXDOMAIN looking up A for [www.thehomeofmyown.com](http://www.thehomeofmyown.com) - check that a DNS record exists for this domain

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.  
Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.  
root@thehomeofmyown:~#

My web server is (include version): Vultr 104.207.130.242 WordPress ???

The operating system my web server runs on is (include version): Ubuntu 20.04 x64

My hosting provider, if applicable, is: Vultr

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): terminal

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): ???

---

<div class="post-metadata">

**Author:** ![bruncsak](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/bruncsak/32/18414_2.png) [@bruncsak](https://community.letsencrypt.org/u/bruncsak)\
**Post date:** [January 11, 2022, 10:30am UTC](https://community.letsencrypt.org/t/ssl-certificat-problem/169468/2 "2022-01-11T10:30:59Z")

</div>

The problem is what the error message says. There is no DNS address record for `www.thehomeofmyown.com` in the name server. If you want that domain name, add it into the DNS, probably pointing to the apex domain name `thehomeofmyown.com`, which already has an address record: 104.207.130.242.

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [January 11, 2022, 4:04pm UTC](https://community.letsencrypt.org/t/ssl-certificat-problem/169468/3 "2022-01-11T16:04:54Z")

</div>

> [@ChristianPudenz](#):
>
> 151 updates can be applied immediately.

Do you update your system?

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [January 11, 2022, 4:05pm UTC](https://community.letsencrypt.org/t/ssl-certificat-problem/169468/4 "2022-01-11T16:05:27Z")

</div>

I now see it backward.  
The "www" has an IP - but the apex doesn't ☹

---

<div class="post-metadata">

**Author:** ![ChristianPudenz](https://avatars.discourse-cdn.com/v4/letter/c/3da27b/32.png) [@ChristianPudenz](https://community.letsencrypt.org/u/ChristianPudenz)\
**Post date:** [January 14, 2022, 11:50am UTC](https://community.letsencrypt.org/t/ssl-certificat-problem/169468/5 "2022-01-14T11:50:40Z")

</div>

I still have problems with linking my domain. Now I cannot open wordpress. And if I try to get a ssl certificate there is this error:

root@thehomeofmyown:~# certbot --nginx --redirect -d [www.thehomeofmyown.com](http://www.thehomeofmyown.com) -d [thehomeofmyown.com](http://thehomeofmyown.com) -m [admin@thehomeofmyown.com](mailto:admin@thehomeofmyown.com) --agree-tos --no-eff-email  
Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Requesting a certificate for [www.thehomeofmyown.com](http://www.thehomeofmyown.com) and [thehomeofmyown.com](http://thehomeofmyown.com)

Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:  
Domain: [thehomeofmyown.com](http://thehomeofmyown.com)  
Type: dns  
Detail: no valid A records found for [thehomeofmyown.com](http://thehomeofmyown.com); no valid AAAA records found for [thehomeofmyown.com](http://thehomeofmyown.com)

Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to this nginx server and that it is accessible from the internet.

Some challenges have failed.  
Ask for help or search for solutions at [https://community.letsencrypt.org](https://community.letsencrypt.org). See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.  
root@thehomeofmyown:~#

Now under google domains I point the a record to \*\*www.\*\*[thehomeofmyown.com](http://thehomeofmyown.com).

Maybe someone can help me to figure it out.

Maybe I can somehow start all over again or fix the error. Already tired trying

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [January 14, 2022, 12:26pm UTC](https://community.letsencrypt.org/t/ssl-certificat-problem/169468/6 "2022-01-14T12:26:17Z")

</div>

If you want a certificate for both hostnames, your DNS should be configured for _both_ too. How you're writing it, it sounds like you changed your DNS by modifying the previous record for `thehomeofmyown.com` to `www.thehomeofmyown.com` whereas you should have _added_ a second record.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [February 13, 2022, 12:26pm UTC](https://community.letsencrypt.org/t/ssl-certificat-problem/169468/7 "2022-02-13T12:26:41Z")

</div>

Closed on February 13, 2022, 12:26pm UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
