# Error getting validation data (2)

**URL:** <https://community.letsencrypt.org/t/error-getting-validation-data-2/58217>\
**Category:** Help\
**Created:** [March 31, 2018, 3:32am UTC](https://community.letsencrypt.org/t/error-getting-validation-data-2/58217 "2018-03-31T03:32:21Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![joombler](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/joombler/32/25119_2.png) [@joombler](https://community.letsencrypt.org/u/joombler)\
**Post date:** [March 31, 2018, 3:32am UTC](https://community.letsencrypt.org/t/error-getting-validation-data-2/58217/1 "2018-03-31T03:32:21Z")

</div>

Dear team,  
Just ran into an issue after you updated the FreeBSD dehydrated port some time ago.  
Current version: dehydrated-0.6.1.7

Can you tell me if this is a server time out issue or is it caused by the recent update?  
best regards, Jos

My domain is: cloudzeeland.nl  
I ran this command: periodic weekly (FreeBSD)  
My web server is (include version): apache24-2.4.33  
The operating system my web server runs on is (include version): FreeBSD 10

It produced this output:

* * *

Checking Let’s Encrypt certificate status:

# INFO: Using main config file /usr/local/etc/dehydrated/config

Processing cloudzeeland.nl with alternative names: www.cloudzeeland.nl

- Checking domain name(s) of existing cert… unchanged.
- Checking expire date of existing cert…
- Valid till Apr 26 11:37:22 2018 GMT (Less than 30 days). Renewing!
- Signing domains…
- Generating private key…
- Generating signing request…
- Requesting authorization for cloudzeeland.nl…
- Requesting authorization for www.cloudzeeland.nl…
- 2 pending challenge(s)
- Deploying challenge tokens…
- Responding to challenge for cloudzeeland.nl authorization…  
ERROR: Challenge is invalid! (returned: invalid) (result: {  
“type”: “http-01”,  
“status”: “invalid”,  
“error”: {  
“type”: “urn:acme:error:connection”,  
“detail”: “Fetching [https://www.cloudzeeland.nl.well-known/acme-challenge/\_SfVw162d3Hadrqy0mH07klmeWON-GrM9uf7cdzpr0c:](https://www.cloudzeeland.nl.well-known/acme-challenge/_SfVw162d3Hadrqy0mH07klmeWON-GrM9uf7cdzpr0c:) Error getting validation data”,  
“status”: 400

* * *

---

<div class="post-metadata">

**Author:** ![mnordhoff](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/mnordhoff/32/22583_2.png) [@mnordhoff](https://community.letsencrypt.org/u/mnordhoff)\
**Post date:** [March 31, 2018, 3:51am UTC](https://community.letsencrypt.org/t/error-getting-validation-data-2/58217/2 "2018-03-31T03:51:33Z")

</div>

> [@joombler](#):
>
> Fetching [https://www.cloudzeeland.nl.well-known/acme-challenge/\_SfVw162d3Hadrqy0mH07klmeWON-GrM9uf7cdzpr0c](https://www.cloudzeeland.nl.well-known/acme-challenge/_SfVw162d3Hadrqy0mH07klmeWON-GrM9uf7cdzpr0c)

The server is redirecting `http://www.cloudzeeland.nl/abc` to `https://www.cloudzeeland.nlabc`.

Check the Apache configuration for something like "`Redirect / https://www.cloudzeeland.nl`" and add a "`/`" to the end so it's "`Redirect / https://www.cloudzeeland.nl/`".

---

<div class="post-metadata">

**Author:** ![joombler](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/joombler/32/25119_2.png) [@joombler](https://community.letsencrypt.org/u/joombler)\
**Post date:** [March 31, 2018, 5:33am UTC](https://community.letsencrypt.org/t/error-getting-validation-data-2/58217/3 "2018-03-31T05:33:15Z")

</div>

Thanks, that worked! Much appreciated.

---

<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:** [April 30, 2018, 5:33am UTC](https://community.letsencrypt.org/t/error-getting-validation-data-2/58217/4 "2018-04-30T05:33:25Z")

</div>

Closed on April 30, 2018, 5:33am UTC

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