# MacOS Failed authorization procedure

**URL:** <https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559>\
**Category:** Help\
**Created:** [January 27, 2017, 5:39pm UTC](https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559 "2017-01-27T17:39:26Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![samarpanda](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/samarpanda/32/10797_2.png) [@samarpanda](https://community.letsencrypt.org/u/samarpanda)\
**Post date:** [January 27, 2017, 5:39pm UTC](https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559/1 "2017-01-27T17:39:26Z")

</div>

My domain is: [samarpanda.com](http://samarpanda.com)

I ran this command in my laptop: certbot certonly --webroot --staging -w . -d [samarpanda.com](http://samarpanda.com) --config-dir . --logs-dir . --work-dir .  
Saving debug log to /Users/samar/projects/me-1/letsencrypt.log  
Obtaining a new certificate  
Performing the following challenges:  
http-01 challenge for [samarpanda.com](http://samarpanda.com)  
Using the webroot path /Users/samar/projects/me-1 for all unmatched domains.  
Waiting for verification…  
Cleaning up challenges  
Failed authorization procedure. [samarpanda.com](http://samarpanda.com) (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from [http://samarpanda.com/.well-known/acme-challenge/NFoCBt6DwobdNmAaETZIyyjQahlh3Kg6KV--Cg71bo8:](http://samarpanda.com/.well-known/acme-challenge/NFoCBt6DwobdNmAaETZIyyjQahlh3Kg6KV--Cg71bo8:) "

404 Not Found
# Not Found
\<p"

IMPORTANT NOTES:

- The following errors were reported by the server:

My operating system is (include version): MacOS Sierra Version: 10.12.3 (16D32)

My web server is (include version):

My hosting provider, if applicable, is: Smallorange. Its a shared server and i don’t have root access.

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

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [January 27, 2017, 6:15pm UTC](https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559/2 "2017-01-27T18:15:01Z")

</div>

The webroot looks incorrect in your command. What is the folder which is the top level of your website ? i.e. where the main index.htm or index.php is usually. This is the folder you should be defining in the command.

---

<div class="post-metadata">

**Author:** ![samarpanda](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/samarpanda/32/10797_2.png) [@samarpanda](https://community.letsencrypt.org/u/samarpanda)\
**Post date:** [January 27, 2017, 6:51pm UTC](https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559/3 "2017-01-27T18:51:51Z")

</div>

I am running this command from my laptop locally not in my hosting server. But still if i ran as per server webroot path i.e

Samars-MacBook-Pro:me-1 samar$ certbot certonly --webroot --agree-tos -w /home/samarpan/public\_html -d [samarpanda.com](http://samarpanda.com) --config-dir . --logs-dir . --work-dir .

/home/samarpan/public\_html does not exist or is not a directory

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [January 27, 2017, 7:09pm UTC](https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559/4 "2017-01-27T19:09:12Z")

</div>

certbot needs to be on the same server as webroot files.

Do you want to specifically run it from your MAC ? You could use the DNS challenge from your MAC if that works (it requires a token copied as a TXT record to your DNS )

---

<div class="post-metadata">

**Author:** ![samarpanda](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/samarpanda/32/10797_2.png) [@samarpanda](https://community.letsencrypt.org/u/samarpanda)\
**Post date:** [January 27, 2017, 7:56pm UTC](https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559/5 "2017-01-27T19:56:06Z")

</div>

Yes, i want to run it from my MAC. Sorry, couldn’t get you how to use this DNS challenge from my MAC. Where do i get this token? Could you please elaborate?

---

<div class="post-metadata">

**Author:** ![serverco](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/serverco/32/4251_2.png) [@serverco](https://community.letsencrypt.org/u/serverco)\
**Post date:** [January 27, 2017, 8:08pm UTC](https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559/6 "2017-01-27T20:08:57Z")

</div>

If you want to run it remotely from your MAC, there are 2 relatively easy options that I can think of.

1. using the DNS challenge - see the [certbot documentation](https://certbot.eff.org/docs/using.html#commands). If you use the “–preferred-challenges dns-01” then certbot will provide you with the “token” that needs to be added to your DNS records.

2. using the webroot method you can use [GetSSL](https://github.com/srvrco/getssl), one of the [alternate clients](https://letsencrypt.org/docs/client-options/), which is designed to copy the files for webroot using FTP, SFTP or SSH for validation

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\
**Post date:** [February 26, 2017, 8:15pm UTC](https://community.letsencrypt.org/t/macos-failed-authorization-procedure/26559/7 "2017-02-26T20:15:20Z")

</div>

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