<p>I'm trying to generate a certificate in my local (MacBook) environment which I can package in my Docker image and deploy into my AWS environment via Kubernetes.</p>

<p>I've scoured sources online for a solution to this but I'm unable to find the details I need.</p>

<p>From my macbook:</p>

<pre><code>sudo certbot certonly -a standalone -d my.domain
</code></pre>

<p>Gives me this error:</p>

<pre><code>Failed authorization procedure. my.domain (http-01): urn:acme:error:unauthorized :: 
The client lacks sufficient authorization :: Invalid response from 
http://my.domain/.well-known/acme-challenge/T8jtGQswRuMgHKIhGvb-
QD73kytTZnHfH5mK5lEZUJc: "{"timestamp":"2018-04-22T22:33:40.845+0000","status":404,
"error":"Not Found","message":"No message available","path":"/.well-kno"
</code></pre>

<p>Clearly, I need a way to prove that I own my own domain. How can I do this locally?</p>

<p>In order to verify ownership of the domain from your macbook you have these two options as stated in the certbot docs:</p>

<ul>
<li>Use a DNS plugin - <a href="https://certbot.eff.org/docs/using.html#dns-plugins" rel="nofollow noreferrer">https://certbot.eff.org/docs/using.html#dns-plugins</a></li>
<li>Use the manual method - <a href="https://certbot.eff.org/docs/using.html#manual" rel="nofollow noreferrer">https://certbot.eff.org/docs/using.html#manual</a></li>
</ul>

<p>While the standalone option does not require web server software it does require that it is run on the target web server - it is therefore not what you need to do and will result in the failure reported in your question.</p>
