# No valid IP addresses found for my domain

**URL:** <https://community.letsencrypt.org/t/no-valid-ip-addresses-found-for-my-domain/110434>\
**Category:** Help\
**Created:** [January 13, 2020, 4:03am UTC](https://community.letsencrypt.org/t/no-valid-ip-addresses-found-for-my-domain/110434 "2020-01-13T04:03:18Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![jeraldsabum](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/jeraldsabum/32/36374_2.png) [@jeraldsabum](https://community.letsencrypt.org/u/jeraldsabum)\
**Post date:** [January 13, 2020, 4:03am UTC](https://community.letsencrypt.org/t/no-valid-ip-addresses-found-for-my-domain/110434/1 "2020-01-13T04:03:18Z")

</div>

I'm facing issues in generating Letsencrypt SSL certificates for a domain mapped to a private address. (192.168.19.15)

My domain is: [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com) and its a public domain (Verified from [DNS Checker - DNS Check Propagation Tool](https://dnschecker.org/#A/elk.internal.mindcurv.com))

> jerald@jeraldsm:~$ nslookup [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> Server: 127.0.0.53  
> Address: 127.0.0.53#53
> 
> Non-authoritative answer:  
> Name: [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> Address: 192.168.19.15

I ran this command for generating SSL certificate:  
./letsencrypt-auto certonly --standalone -d [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)

**It produced the following output:**

> [root@elk-slreport letsencrypt]# ./letsencrypt-auto certonly --standalone -d [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> Saving debug log to /var/log/letsencrypt/letsencrypt.log  
> Plugins selected: Authenticator standalone, Installer None  
> Obtaining a new certificate  
> Performing the following challenges:  
> http-01 challenge for [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> Waiting for verification...  
> Challenge failed for domain [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> http-01 challenge for [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> Cleaning up challenges  
> Some challenges have failed.
> 
> IMPORTANT NOTES:
> 
> - The following errors were reported by the server:

I have also tried using the command "cerbot --apache". This one also failed with similar error:

> [root@elk-slreport ~]# certbot --apache  
> Saving debug log to /var/log/letsencrypt/letsencrypt.log  
> Plugins selected: Authenticator apache, Installer apache  
> Starting new HTTPS connection (1): [acme-v02.api.letsencrypt.org](http://acme-v02.api.letsencrypt.org)
> 
> Which names would you like to activate HTTPS for?
> 
> * * *
> 
> 1: [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)
> 
> * * *
> 
> Select the appropriate numbers separated by commas and/or spaces, or leave input  
> blank to select all options shown (Enter 'c' to cancel): 1  
> Obtaining a new certificate  
> Performing the following challenges:  
> http-01 challenge for [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> Waiting for verification...  
> Challenge failed for domain [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> http-01 challenge for [elk.internal.mindcurv.com](http://elk.internal.mindcurv.com)  
> Cleaning up challenges  
> Some challenges have failed.
> 
> IMPORTANT NOTES:
> 
> - The following errors were reported by the server:

The operating system my web server runs on is (include version): CentOS Linux release 7.7.1908 (Core)

My hosting provider, if applicable, is: Apache/2.4.6

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 0.39.0

Is it possible to issue a certificate for private IP address ?  
Thanks in advance!.

---

<div class="post-metadata">

**Author:** ![danb35](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/danb35/32/70869_2.png) [@danb35](https://community.letsencrypt.org/u/danb35)\
**Post date:** [January 13, 2020, 6:19am UTC](https://community.letsencrypt.org/t/no-valid-ip-addresses-found-for-my-domain/110434/2 "2020-01-13T06:19:40Z")

</div>

> [@jeraldsabum](#):
>
> I’m facing issues in generating Letsencrypt SSL certificates for a domain mapped to a private address. (192.168.19.15)

This isn't going to be possible without using DNS validation to obtain the cert.

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [January 13, 2020, 2:09pm UTC](https://community.letsencrypt.org/t/no-valid-ip-addresses-found-for-my-domain/110434/3 "2020-01-13T14:09:02Z")

</div>

As an alternative, if you like split-horizon DNS, you could potentially set something up where `elk.internal.mindcurv.com` has a routable IP in the external view. E.g. the machine’s own IP, or another machine running a reverse proxy web server…

I’m not endorsing it, just saying you have options. Increasingly complicated and customized options.

---

<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 12, 2020, 2:09pm UTC](https://community.letsencrypt.org/t/no-valid-ip-addresses-found-for-my-domain/110434/4 "2020-02-12T14:09:03Z")

</div>

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