# Invalid response from server (type = unauthorized)

**URL:** <https://community.letsencrypt.org/t/invalid-response-from-server-type-unauthorized/49925>\
**Category:** Help\
**Created:** [January 9, 2018, 3:59pm UTC](https://community.letsencrypt.org/t/invalid-response-from-server-type-unauthorized/49925 "2018-01-09T15:59:04Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![altf4](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/altf4/32/19187_2.png) [@altf4](https://community.letsencrypt.org/u/altf4)\
**Post date:** [January 9, 2018, 3:59pm UTC](https://community.letsencrypt.org/t/invalid-response-from-server-type-unauthorized/49925/1 "2018-01-09T15:59:04Z")

</div>

Hello Community,

after I got a great and helpful answer I have another little problem while generating an new certificate on my server.

Server: Debian, Virtualmin, Apache2

**The following command…**  
cd /root/letsencrypt/ && ./letsencrypt-auto certonly --email [postmaster@bonebase.eu](mailto:postmaster@bonebase.eu) --agree-tos --webroot --renew-by-default -w /home/bonebase/public\_html/ -d [www.bonebase.eu](http://www.bonebase.eu) -d [bonebase.eu](http://bonebase.eu) -d [mail.bonebase.eu](http://mail.bonebase.eu) --authenticator webroot && cp /etc/letsencrypt/live/www.bonebase.eu/cert.pem /home/bonebase/ssl\_certificates/cert.pem && cp -f /etc/letsencrypt/live/www.bonebase.eu/chain.pem /home/bonebase/ssl\_certificates/chain.pem && cp -f /etc/letsencrypt/live/www.bonebase.eu/fullchain.pem /home/bonebase/ssl\_certificates/fullchain.pem && cp -f /etc/letsencrypt/live/www.bonebase.eu/privkey.pem /home/bonebase/ssl\_certificates/privkey.pem

**…throws the following output…**  
Saving debug log to /var/log/letsencrypt/letsencrypt.log  
Plugins selected: Authenticator webroot, Installer None  
Renewing an existing certificate  
Performing the following challenges:  
http-01 challenge for [www.bonebase.eu](http://www.bonebase.eu)  
http-01 challenge for [bonebase.eu](http://bonebase.eu)  
http-01 challenge for [mail.bonebase.eu](http://mail.bonebase.eu)  
Using the webroot path /home/bonebase/public\_html for all unmatched domains.  
Waiting for verification…  
Cleaning up challenges  
Failed authorization procedure. [mail.bonebase.eu](http://mail.bonebase.eu) (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from [http://mail.bonebase.eu/.well-known/acme-challenge/Xe\_nMMfSEuw9VY9JN74UxLJerUXqoxvCJvhuKzaOKdY:](http://mail.bonebase.eu/.well-known/acme-challenge/Xe_nMMfSEuw9VY9JN74UxLJerUXqoxvCJvhuKzaOKdY:) "

 \<meta name="viewport" content="width=device-width, initia", bonebase.eu (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://bonebase.eu/.well-known/acme-challenge/ZRymT80gapy9UtVtXPMxQ2qzyst75JTZkvqElT\_nzmw: " \<meta name="viewport" content="width=device-width, initia", www.bonebase.eu (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: Invalid response from http://www.bonebase.eu/.well-known/acme-challenge/xREMoqY-iEwmJYRC1y2yNHJ2wFbVSQJwc0d8LXdz7V4: " \<meta name="viewport" content="width=device-width, initia"

IMPORTANT NOTES:

- The following errors were reported by the server:

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [January 10, 2018, 4:57am UTC](https://community.letsencrypt.org/t/invalid-response-from-server-type-unauthorized/49925/2 "2018-01-10T04:57:16Z")

</div>

Can you create files in `/home/bonebase/public_html` that are then visible under [http://mail.bonebase.eu/](http://mail.bonebase.eu/)? It looks like you have a blanket redirect from anything under [http://mail.bonebase.eu/](http://mail.bonebase.eu/) to the HTTPS version of the site (not preserving the directory path!) which is interfering with the challenge here.

---

<div class="post-metadata">

**Author:** ![schoen](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/schoen/32/79_2.png) [@schoen](https://community.letsencrypt.org/u/schoen)\
**Post date:** [January 10, 2018, 5:00am UTC](https://community.letsencrypt.org/t/invalid-response-from-server-type-unauthorized/49925/3 "2018-01-10T05:00:43Z")

</div>

It looks like this was already discussed at

> [@Certificate renewal fail](https://community.letsencrypt.org/t/certificate-renewal-fail/49893):
>
> H…

A version of the redirect that was the problem there is also apparently the problem here.

---

<div class="post-metadata">

**Author:** ![altf4](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/altf4/32/19187_2.png) [@altf4](https://community.letsencrypt.org/u/altf4)\
**Post date:** [January 10, 2018, 10:19am UTC](https://community.letsencrypt.org/t/invalid-response-from-server-type-unauthorized/49925/4 "2018-01-10T10:19:38Z")

</div>

Hi there,  
it’s possible to create files.  
[https://mail.bonebase.eu/test.txt](https://mail.bonebase.eu/test.txt)

Actually if ceated manually the directory “acme-challenge” produced the following output from virtualmin:  
Requesting a certificate for [bonebase.eu](http://bonebase.eu), [www.bonebase.eu](http://www.bonebase.eu) from Let’s Encrypt …  
… request failed : Web-based validation failed : The native Let’s Encrypt client was used previously on this system, and must be used for all future certificate requests DNS-based validation failed : The native Let’s Encrypt client was used previously on this system, and must be used for all future certificate requests

---

<div class="post-metadata">

**Author:** ![altf4](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/altf4/32/19187_2.png) [@altf4](https://community.letsencrypt.org/u/altf4)\
**Post date:** [January 11, 2018, 10:38am UTC](https://community.letsencrypt.org/t/invalid-response-from-server-type-unauthorized/49925/5 "2018-01-11T10:38:27Z")

</div>

Hi, no. That is another (solved) Problem…

---

<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 10, 2018, 10:38am UTC](https://community.letsencrypt.org/t/invalid-response-from-server-type-unauthorized/49925/6 "2018-02-10T10:38:46Z")

</div>

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