Requesting Network is unreachable

Just for test in a local apache server to check communication between server and

My domain
I ran this command: sudo certbot certonly --apache

It produced this output:
Requesting Network is unreachable

My web server is (include version):Apache 2.4.37 Centos8
My hosting provider, if applicable, is:local on my network
I can login to a root shell on my machine 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 :1.5.0

curl -v works perfectly with no error

We use a Proxy, before the command certbot we run:
export http_proxy="http://x.x.x.x:xxxx and https also

Letsencrypt logs
2020-07-07 08:46:45,129:DEBUG:urllib3.connectionpool:Starting new HTTPS connection (1):
2020-07-07 08:47:30,189:DEBUG:certbot._internal.log:Exiting abnormally:

Possible that the proxy don’t allow the access during the script ?


Hi @claude73

what says


same with

To Letsencrypt, every step should answer.

1 Like

But with traceroute for any site we don’t have icmp allowed in the FW

I use export " export http_proxy=“http://x.x.x.x:xxxx” before curl
and also before the certbot command

I see TCP MISS in the Proxy CONNECT - DIRECT/
8 try and nothing after


Hi, traceroute is not working, but the proxy refuse icmp and other way accross firewall is forbiden.

when I use curl command I use the proxy and it’s good.

But Certbot command " HTTPSConnectionPool(host=‘’, port=443"
try to pass out of proxy and it’s not possible
I don’t understand why with export https defined before Certbot don’t use the proxy ?


With the bypass of proxy it’s now possible to start the Certbot configuration
The computer used for generate the certicat is not the target server
during the http01-challenge too many redirect message
the apps cannot access to domaine/directory
Redirect is only http to https

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