# Redirect to https causing problems

**URL:** https://community.letsencrypt.org/t/redirect-to-https-causing-problems/60531
**Category:** Help
**Created:** [April 26, 2018, 6:28pm UTC](https://community.letsencrypt.org/t/redirect-to-https-causing-problems/60531 "2018-04-26T18:28:32Z")
**Posts on this page:** 1
**Showing post:** 6

<div class="post-metadata">

### Author: ![bytecamp](https://avatars.discourse-cdn.com/v4/letter/b/54ee81/32.png) [@bytecamp](https://community.letsencrypt.org/u/bytecamp)
#### Post date: [April 27, 2018, 1:05pm UTC](https://community.letsencrypt.org/t/redirect-to-https-causing-problems/60531/6 "2018-04-27T13:05:00Z")

</div>

Have a look at your redirect chain:

> $ wget --no-check-certificate -S -O/dev/null '[http://bridgingnursing.com/.well-known/acme-challenge/foo](http://bridgingnursing.com/.well-known/acme-challenge/foo)'

> --2018-04-27 15:01:44-- [http://bridgingnursing.com/.well-known/acme-challenge/foo](http://bridgingnursing.com/.well-known/acme-challenge/foo)  
> HTTP/1.1 301 Moved Permanently  
> Date: Fri, 27 Apr 2018 13:01:54 GMT  
> Server: Apache/2.2.15 (CentOS)  
> **Location: [https://bridgingnursing.com/.well-known/acme-challenge/foo](https://bridgingnursing.com/.well-known/acme-challenge/foo)**  
> Content-Length: 351  
> Connection: close  
> Content-Type: text/html; charset=iso-8859-1  
> --2018-04-27 15:01:44-- [https://bridgingnursing.com/.well-known/acme-challenge/foo](https://bridgingnursing.com/.well-known/acme-challenge/foo)  
> HTTP/1.1 302 Found  
> Date: Fri, 27 Apr 2018 13:01:55 GMT  
> Server: Apache/2.2.15 (CentOS)  
> X-Powered-By: PHP/5.6.36  
> **Location: [https://faculty.nipissingu.ca/](https://faculty.nipissingu.ca/)**  
> Content-Length: 0  
> Connection: close  
> Content-Type: text/html; charset=UTF-8  
> --2018-04-27 15:01:45-- [https://faculty.nipissingu.ca/](https://faculty.nipissingu.ca/)  
> HTTP-Anforderung gesendet, warte auf Antwort...  
> HTTP/1.1 200 OK  
> Date: Fri, 27 Apr 2018 13:01:55 GMT  
> Server: Apache/2.2.15 (CentOS)  
> X-Powered-By: PHP/5.6.36  
> Link: [https://faculty.nipissingu.ca/wp-json/](https://faculty.nipissingu.ca/wp-json/); rel="[https://api.w.org/](https://api.w.org/)"  
> Connection: close  
> Transfer-Encoding: chunked  
> Content-Type: text/html; charset=UTF-8

Is this intended?  
You should definitly exclude any PHP handler for /.well-known/acme-challenge on your server, otherwise the files certbot creates will not be delivered at all. This is clearly visible in the output of the certbot command:

> [@verdonv](#):
>
> Attempting to renew cert (bridgingnursing.ca) from /etc/letsencrypt/renewal/bridgingnursing.ca.conf produced an unexpected error: Failed authorization procedure. [bridgingnursing.com](http://bridgingnursing.com) (http-01): urn:acme:error:unauthorized :: The client lacks sufficient authorization :: **Invalid response** from [http://bridgingnursing.com/.well-known/acme-challenge/u5xnsCvd8SPSXr9CxcyhUHzP0AZjzc7oiOPczVBB7Aw:](http://bridgingnursing.com/.well-known/acme-challenge/u5xnsCvd8SPSXr9CxcyhUHzP0AZjzc7oiOPczVBB7Aw:) "
> 
> **\<!–[if IE 7]\>**

---

_[View the full topic](https://community.letsencrypt.org/t/redirect-to-https-causing-problems/60531)._