Skip to content
This repository has been archived by the owner on Jan 16, 2020. It is now read-only.

Missing .well-known directory #74

Open
ont4300 opened this issue Jul 4, 2018 · 1 comment
Open

Missing .well-known directory #74

ont4300 opened this issue Jul 4, 2018 · 1 comment

Comments

@ont4300
Copy link

ont4300 commented Jul 4, 2018

I have run your script following the instructions that you gave. It fails when doing the challenge for the domain name with a missing .well-known/acme-challenge/... data.

Do I have to create that directory structure first? I can not find the file in the public folder for the app.

The results follow:

Obtaining a new certificate
Performing the following challenges:
http-01 challenge for www.tomcloud.glsys.ca
http-01 challenge for tomcloud.glsys.ca
Using the webroot path /srv/users/serverpilot/apps/owncloud/public for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. tomcloud.glsys.ca (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://tomcloud.glsys.ca/.well-known/acme-challenge/11XTOeY0HiV7LAGXn7sZ-ouh9KxPpgByJm3JKOf9GPs: "

@ont4300
Copy link
Author

ont4300 commented Jul 5, 2018

Never mind. I finally read the letsencrypt log and saw what's going on.

Tom.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant