https://www.lonesomecrowdedweb.com/tags/nginx/ Recent content in Nginx on The Lonesome Crowded Web https://www.lonesomecrowdedweb.com/papermod-cover.png https://www.lonesomecrowdedweb.com/papermod-cover.png Hugo -- 0.149.0 en Tue, 21 Feb 2017 00:00:00 +0000 https://www.lonesomecrowdedweb.com/blog/broken-redirect/ Tue, 21 Feb 2017 00:00:00 +0000 https://www.lonesomecrowdedweb.com/blog/broken-redirect/ <p>I was recently trying to renew the Let&rsquo;s Encrypt certificate for this site, but doing so failed with the following error (and an accompanying 404 Not Found):</p> <div class="highlight"><pre tabindex="0" class="chroma"><code class="language-plaintext" data-lang="plaintext"><span class="line"><span class="cl">Cert is due for renewal, auto-renewing... </span></span><span class="line"><span class="cl">Renewing an existing certificate </span></span><span class="line"><span class="cl">Performing the following challenges: </span></span><span class="line"><span class="cl">http-01 challenge for lonesomecrowdedweb.com </span></span><span class="line"><span class="cl">http-01 challenge for www.lonesomecrowdedweb.com </span></span><span class="line"><span class="cl">Waiting for verification... </span></span><span class="line"><span class="cl">Cleaning up challenges </span></span><span class="line"><span class="cl">Attempting to renew cert from /etc/letsencrypt/renewal/lonesomecrowdedweb.com.conf produced an unexpected error: Failed authorization procedure. www.lonesomecrowdedweb.com (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization </span></span><span class="line"><span class="cl"> </span></span><span class="line"><span class="cl">Domain: www.lonesomecrowdedweb.com </span></span><span class="line"><span class="cl">Type: unauthorized </span></span><span class="line"><span class="cl">Detail: Invalid response from http://www.lonesomecrowdedweb.com/.well-known/acme-challenge/ ... </span></span></code></pre></div><p>This was because my redirects in NGINX were not configured appropriately, and I didn&rsquo;t notice due to my use of <a href="https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security">HTTP Strict-Transport-Security</a>. Correcting the bindings allowed me to renew the certificate successfully.</p>