# No route to host when I ran certbot

**URL:** <https://community.letsencrypt.org/t/no-route-to-host-when-i-ran-certbot/183645>\
**Category:** Help\
**Created:** [August 30, 2022, 4:04am UTC](https://community.letsencrypt.org/t/no-route-to-host-when-i-ran-certbot/183645 "2022-08-30T04:04:10Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nguyenanhdung191](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/nguyenanhdung191/32/63529_2.png) [@nguyenanhdung191](https://community.letsencrypt.org/u/nguyenanhdung191)\
**Post date:** [August 30, 2022, 4:04am UTC](https://community.letsencrypt.org/t/no-route-to-host-when-i-ran-certbot/183645/1 "2022-08-30T04:04:10Z")

</div>

My domain is: dhis2.la

I ran this command: certbot certonly --non-interactive --standalone --agree-tos -m [nguyenanhdung191@gmail.com](mailto:nguyenanhdung191@gmail.com) -d dhis2.la

It produced this output: Requesting [acme-v02.api.letsencrypt.org/directory:](http://acme-v02.api.letsencrypt.org/directory:) No route to host

Operating system: Ubuntu 20.04

---

<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:** [August 30, 2022, 4:08am UTC](https://community.letsencrypt.org/t/no-route-to-host-when-i-ran-certbot/183645/2 "2022-08-30T04:08:16Z")

</div>

Hi @nguyenanhdung191, and welcome to the LE community forum 🙂

Seems like a routing issue...  
Please show the outputs of:  
`nslookup acme-v02.api.letsencrypt.org`  
`netstat -nr`  
`ifconfig | grep inet`

---

<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:** [August 30, 2022, 4:15am UTC](https://community.letsencrypt.org/t/no-route-to-host-when-i-ran-certbot/183645/3 "2022-08-30T04:15:38Z")

</div>

After we fix the routing issue, we need to address the use of `--standalone`.  
Noting that there is a web server responding:

```nohighlight
curl -Ii http://dhis2.la/.well-known/acme-challenge/Test_File-1234
HTTP/1.1 403 Forbidden
Date: Tue, 30 Aug 2022 04:14:02 GMT
Server: Apache
Content-Type: text/html; charset=iso-8859-1

```

---

<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:** [September 29, 2022, 4:15am UTC](https://community.letsencrypt.org/t/no-route-to-host-when-i-ran-certbot/183645/4 "2022-09-29T04:15:48Z")

</div>

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