Lestencrypt isuue while install cerbot certficate

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. crt.sh | 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:
I ran this command:
sudo certbot --apache -d alexpublishing.com

It produced this output:
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
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for alexpublishing.com
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. alexpublishing.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://ww12.alexpublishing.com/.well-known/acme-challenge/D0Y53RVflVTbbxf4a8QVibfp8R-7e3SNQiPvPXvohzM: 404


My web server is (include version):

The operating system my web server runs on is (include version):
win 10
My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don't know):
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

First, EFF has announced the end of support for Certbot on Windows. You may want to consider switching to a different ACME Client. See This Link for the announcement along with migration path.

As to this problem, a cert challenge request for alexpublishing.com is being redirected to ww12.alexpublishing.com. You use the Apache plugin which should have updated your Apache to handle the request without redirect.

To me it looks like this redirect happens by something in front of Apache. Maybe a router or firewall of some kind. Are you sure HTTP requests to that domain reach the Apache server?

Because usually we see other response headers when Apache used. Sometimes we don't but that is rare. For what it's worth, the ww12 subdomain is handled by nginx but that shouldn't even be involved. And ww12 looks like some sort of parking service.

Even requests for the "home" page get redirected to ww12

curl -i http://alexpublishing.com
HTTP/1.1 302 Found
content-length: 0
location: http://ww12.alexpublishing.com/
cache-control: no-cache
1 Like

You need to review your Apache config.
httpd.exe -t -D DUMP_VHOSTS


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