Type: unauthorized Detail: Invalid response from

Help
21

Hmm... let me think a minute... :thinking:

1 Like
22

Just to get a reference out there:

1 Like
23

Do you have a folder named .well-known in /var/www/html ?

1 Like
24

Lets encrypt command throwing the same error even with the default Apache2 page.

I already been through with this blog, I have spent around 4 hours then I posted here.

Screenshot from 2020-10-10 04-43-28
Screenshot from 2020-10-10 04-43-281855×1019 188 KB

25

You have the wrong certificate installed. We know that, but we can fix it. :slightly_smiling_face:

Complete certificate history:


Screenshot_20201009-172018_Samsung Internet
Screenshot_20201009-172018_Samsung Internet1241×421 245 KB
1 Like
26

Just for the sake of sanity, try this:

sudo certbot certonly --cert-name veritebranded --apache -d "veritebranded.com,www.veritebranded.com" --dry-run

1 Like
27

Output -
sudo certbot certonly --cert-name veritebranded --apache -d "veritebranded.com,www.veritebranded.com" --dry-run
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for veritebranded.com
http-01 challenge for www.veritebranded.com
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. www.veritebranded.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.veritebranded.com/.well-known/acme-challenge/hJ0biZTb-HWZ0ORFN6CUxgxuVG1B-Fofgnj-Xfl5bXo [3.226.242.192]: "\n\n404 Not Found\n\n

Not Found

\n<p", veritebranded.com (http-01): urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://veritebranded.com/.well-known/acme-challenge/MqJN2o3ZaDlBbZKKxuPd0My0sLLpz8PAdNKxAiM8dj0 [3.226.242.192]: "\n\n404 Not Found\n\n

Not Found

\n<p"

IMPORTANT NOTES:

1 Like
28

Something doesn't add up.

Apache is currently serving from /var/www/html/ for that domain, not from /var/www/html/ecom/.

So either:

  • One of these posts is not accurate, or
  • Apache is not restarted, or
  • You have more than one Apache installation (it's not a Bitnami server, is it?)
1 Like
29

It's Magento _az ...

1 Like
30

Yes, I assume Magento is sitting in the ecom/ directory. If you actually visit the domain right now, you see the Ubuntu default Apache page, which is in the directory above it.

veritebranded.com vs veritebranded.com/ecom

If the configuration posted was accurate, you wouldn't need the second URL to see Magento.

31

I think he changed the configuration a moment ago. I'm getting the standard 404 instead of the decorative 404 now. The certbot 404s show it in difference from the original post to the dry run a moment ago.

1 Like
32

I just changed "/var/www/html/ecom/" to "/var/www/html/" to make sure that it is not related to magento so tested with default Apache2 page

1 Like
33

That was my guess. Is there a .well-known in that folder?

1 Like
34

Yes, It is there
:/var/www/html/.well-known$

2 Likes
35

It's not Halloween yet, @_az! :jack_o_lantern:

Don't give me a heart attack! :scream:

I wrote some certbot comedy here:
https://community.letsencrypt.org/t/discussion-the-certificate-handbook/133296/42?u=griffin

1 Like
36

Perfect. Can you create a file named test containing "OK" in /var/www/html/.well-known/acme-challenge/ ?

1 Like
37

Its AWS EC2 instance

1 Like
38

done as you said created test file

1 Like
39

That's OK. :slightly_smiling_face: Just not Bitnami, please no more Bitnami... :crazy_face:

1 Like
40

Beautiful! :smiley: I can see the file!

1 Like