Lets Encrypt Not Looking for ".well-known"

For some reason, it appears that Lets Encrypt is not including ".well-known" in the URL when attempting to validate.

The domain in question has been replaced with example.com for security.

Failed authorization procedure. example.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://example.com/acme-challenge/y33OwEvy3VqJ07hZRlpsYqNO968GSluSboaJR... Error getting validation data, www.example.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://example.com/acme-challenge/XYjGVIrLWqMo99odNABe9WAbjqHq2RgOtLxyq... Error getting validation data, autodiscover.example.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://example.com/acme-challenge/TIKhJ61ACpUAA-sf38BzGfh8rzpzFPB7ukevD... Error getting validation data, autoconfig.example.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://example.com/acme-challenge/-uoeNWjMJceTs69SMihErNM28ZGEytoYGUuB1... Error getting validation data IMPORTANT NOTES: - The following errors were reported by the server:

Domain: example.com Type: connection Detail: Fetching https://example.com/acme- challenge/y33OwEvy3VqJ07hZRlpsYqNO968GSluSboaJR2MYa1I: Error getting validation data

Domain: www.example.com Type: connection Detail: Fetching https://example.com/acme- challenge/XYjGVIrLWqMo99odNABe9WAbjqHq2RgOtLxyqXd93uk: Error getting validation data

Domain: autodiscover.example.com Type: connection Detail: Fetching https://example.com/acme-challenge/TIKhJ61ACpUAA- sf38BzGfh8rzpzFPB7ukevD2hV1ug: Error getting validation data

Domain: autoconfig.example.com Type: connection Detail: Fetching https://example.com/acme- challenge/-uoeNWjMJceTs69SMihErNM28ZGEytoYGUuB1xjh3yc: Error getting validation data

To fix these errors, please make sure that your domain name was entered correctly and the DNS A record(s) for that domain contain(s) the right IP address. Additionally, please check that your computer has a publicly routable IP address and that no firewalls are preventing the server from communicating with the client. If you're using the webroot plugin, you should also verify that you are serving files from the webroot path you provided.