Letsencrypt renew failed


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. 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: goorme.bridgetec.co.kr

I ran this command:letsencrypt renew

It produced this output:

Processing /etc/letsencrypt/renewal/goorme.bridgetec.co.kr.conf

Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for goorme.bridgetec.co.kr
Waiting for verification…
Cleaning up challenges
Attempting to renew cert (goorme.bridgetec.co.kr) from /etc/letsencrypt/renewal/goorme.bridgetec.co.kr.conf produced an unexpected error: Failed authorization procedure. goorme.bridgetec.co.kr (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://goorme.bridgetec.co.kr/.well-known/acme-challenge/yENzkhuiXCD4dG3L9DawCYwPGWZpP7dvkPJuGRKLCKs: Connection refused. Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/goorme.bridgetec.co.kr/fullchain.pem (failure)

All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/goorme.bridgetec.co.kr/fullchain.pem (failure)

1 renew failure(s), 0 parse failure(s)


  • The following errors were reported by the server:

    Domain: goorme.bridgetec.co.kr
    Type: connection
    Detail: Fetching
    Connection refused

    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): Apache/2.4.6(CentOS)

The operating system my web server runs on is (include version): CentOS 7.3?

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 am

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

what’s wrong?

im just trying ‘letsencrypt renew’ but it doesn’t work…


Hi @bsh4227

fetching your file


I have a Bad Request - Message:

Bad Request

Your browser sent a request that this server could not understand.
Reason: You’re speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

You are sending https over port 80, this is wrong. So check your server configuration.

Port 80 must send plain http.

PS: This wrong url


works - https + Port 80


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