Have a look at your redirect chain:
$ wget --no-check-certificate -S -O/dev/null 'http://bridgingnursing.com/.well-known/acme-challenge/foo'
--2018-04-27 15:01:44-- 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
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
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/
Content-Length: 0
Connection: close
Content-Type: text/html; charset=UTF-8
--2018-04-27 15:01:45-- 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/; rel="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: