Requesting new certificat with certbot in manual mode gives error

I followed the instructions and I searched the internet for a solution but I couldn’t find one. I tried a few options but then I reached the try limit in letsencrypt.

I created the file on my web server and gave the name from the certbot output. Initially I thought maybe the online file browser adds some characters in the file so then I created the file in linux and uploaded the file to my server. Same result. The file is accessible (i tested it after uploading it).

Any ideas why do I get the error?

The content of my file is the complete string:

fR3lht3c72K94OsC2HyqyLRHdBpPb8rNRDC_CJFaH7M.Bpq0MuigVWkLJIvzFwNGZ9BWXz3s8TMh70omGAMCHzo

My domain is: http://flavoraddiction.net

I ran this command:sudo certbot certonly --preferred-challenges http -d flavoraddiction.net --manual

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator manual, Installer None
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for flavoraddiction.net

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
NOTE: The IP of this machine will be publicly logged as having requested this
certificate. If you're running certbot in manual mode on a machine that is not
your server, please ensure you're okay with that.

Are you OK with your IP being logged?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
(Y)es/(N)o: Y

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Create a file containing just this data:

fR3lht3c72K94OsC2HyqyLRHdBpPb8rNRDC_CJFaH7M.Bpq0MuigVWkLJIvzFwNGZ9BWXz3s8TMh70omGAMCHzo

And make it available on your web server at this URL:

http://flavoraddiction.net/.well-known/acme-challenge/fR3lht3c72K94OsC2HyqyLRHdBpPb8rNRDC_CJFaH7M

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Press Enter to Continue
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. flavoraddiction.net (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://flavoraddiction.net/.well-known/acme-challenge/fR3lht3c72K94OsC2HyqyLRHdBpPb8rNRDC_CJFaH7M [185.27.134.138]: "<html><body><script type=\"text/javascript\" src=\"/aes.js\" ></script><script>function toNumbers(d){var e=[];d.replace(/(..)/g,func"

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: flavoraddiction.net
   Type:   unauthorized
   Detail: Invalid response from
   http://flavoraddiction.net/.well-known/acme-challenge/fR3lht3c72K94OsC2HyqyLRHdBpPb8rNRDC_CJFaH7M
   [185.27.134.138]: "<html><body><script type=\"text/javascript\"
   src=\"/aes.js\" ></script><script>function toNumbers(d){var
   e=[];d.replace(/(..)/g,func"

   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.

My web server is (include version):nginx

I can login to a root shell on my machine (yes or no, or I don’t know):no

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):yes, but I don’t have access to the version

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

1 Like

Hi @dboyr

see your check, one day old - https://check-your-website.server-daten.de/?q=flavoraddiction.net

J http://flavoraddiction.net/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de 185.27.134.138
200

Fatal: Script /aes.js found. Looks like your hoster has a Bot-Check-Detection, so Letsencrypt can’t check your http-validation file.

That’s a script, may be you or your hoster has installed it.

That blocks Letsencrypt checking your domain.

  • Remove that script (or)
  • use dns validation (or)
  • if both isn’t possible, you can’t use Letsencrypt
3 Likes

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