Let's encrypt didn't work for me,please help


#1

My domain is:
slyy.testapp.win

I ran this command:
./letsencrypt-auto certonly

It produced this output:

Performing the following challenges:
http-01 challenge for slyy.testapp.win
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. slyy.testapp.win (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://slyy.testapp.win/.well-known/acme-challenge/Kexst56VnlPm0lK8YE66DVXDfkXH--DDpYF3qQznB50: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: slyy.testapp.win
    Type: connection
    Detail: Fetching
    http://slyy.testapp.win/.well-known/acme-challenge/Kexst56VnlPm0lK8YE66DVXDfkXH--DDpYF3qQznB50:
    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.

My web server is (include version):

The operating system my web server runs on is (include version):
Cent OS 7.5

My hosting provider, if applicable, is:

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


#2

Do you have any webserver running? I can’t access your site from the internet.


#3

thanks for replying,I suppose to run a tomcat in my server,I didn’t install it yet


#4

I’m going to install a tomcat 8.5


#5

If you don’t have a web server yet, you can use the standalone authenticator.

letsencrypt-auto certonly -a standalone --preferred-challenges http

But you’ll need to make sure that your server’s firewall permits port 80, and that traffic from the internet can reach your server (e.g. ports forwarded on any routers/NAT).

Since your server is in China, you’ll also need to make sure that any website licenses are also sorted out.


#6

thanks,unfortunately 80 port is blocks by the ISP,


#7

In that case, the only alternative is to use DNS validation.

letsencrypt-auto certonly -a manual --preferred-challenges dns-01

However, you need to be able to create TXT records on the testapp.win domain to do this.


#8

I have tried this command,however,it didn’t work as well
[root@localhost letsencrypt]# ./letsencrypt-auto certonly -a standalone --preferred-challenges http
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer None
Please enter in your domain name(s) (comma and/or space separated) (Enter ‘c’
to cancel): slyy.testapp.win
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for slyy.testapp.win
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. slyy.testapp.win (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://slyy.testapp.win/.well-known/acme-challenge/3JmHwQQdwuodVxyxBLJdsYBwc-_v45I-TB7_fl9ks9I: Timeout during connect (likely firewall problem)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: slyy.testapp.win
    Type: connection
    Detail: Fetching
    http://slyy.testapp.win/.well-known/acme-challenge/3JmHwQQdwuodVxyxBLJdsYBwc-_v45I-TB7_fl9ks9I:
    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.


#9

thank you very much,at least this command I have felt the hope,althoght it failed

Obtaining a new certificate
An unexpected error occurred:
There were too many requests of a given type :: Error creating new authz :: too many failed authorizations recently: see https://letsencrypt.org/docs/rate-limits/


#10

That’s okay. That error will be gone after 1 hour and you can try again


#12

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