# Challenge request failed for domain ecofriendlymamacanada.com

**URL:** <https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062>\
**Category:** Help\
**Created:** [September 27, 2017, 1:16am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062 "2017-09-27T01:16:21Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![ecomamacanada](https://avatars.discourse-cdn.com/v4/letter/e/d9b06d/32.png) [@ecomamacanada](https://community.letsencrypt.org/u/ecomamacanada)\
**Post date:** [September 27, 2017, 1:16am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/1 "2017-09-27T01:16:21Z")

</div>

I installed the plug in WP Encrypt on WP and plugged all my info clicked generate certificate and was given 4 lines of certificate and key locations. Didn’t know what to do with it so I called godaddy (my host) and then proceeded to follow the steps to get my CRT. I thought I missed a step when I put in all my info on the WP Encrypt so I deactivated it and deleted all the info and tried again from the beginning but now it says “Challenge request failed for domain [ecofriendlymamacanada.com](http://ecofriendlymamacanada.com)” I’m not sure where to go from here or where to plug in my Certificate request info. I believe my operating system is OS X 10.9.5. My website looks fine in Safari but with Chrome it says “Your connection is not private…” NET::ERR\_CERT\_AUTHORITY\_INVALID

---

<div class="post-metadata">

**Author:** ![ahaw021](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ahaw021/32/14882_2.png) [@ahaw021](https://community.letsencrypt.org/u/ahaw021)\
**Post date:** [September 27, 2017, 3:30am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/2 "2017-09-27T03:30:00Z")

</div>

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. [https://crt.sh/?q=example.com](https://crt.sh/?q=example.com)), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is:

I ran this command:

It produced this output:

My web server is (include version):

The operating system my web server runs on is (include version):

My hosting provider, if applicable, is:

I can login to a root shell on my machine (yes or no, or I don’t know):

I’m using a control panel to manage my site (no, or provide the name and version of the control panel):

---

<div class="post-metadata">

**Author:** ![ahaw021](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/ahaw021/32/14882_2.png) [@ahaw021](https://community.letsencrypt.org/u/ahaw021)\
**Post date:** [September 27, 2017, 3:30am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/3 "2017-09-27T03:30:39Z")

</div>

![image](https://global.discourse-cdn.com/letsencrypt/original/3X/7/a/7a143931ad3e606ead1677560ae56304ee774298.png)

as a volunteer - if you don’t want to use your words i won’t use mine

---

<div class="post-metadata">

**Author:** ![motoko](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/motoko/32/26328_2.png) [@motoko](https://community.letsencrypt.org/u/motoko)\
**Post date:** [September 27, 2017, 3:34am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/4 "2017-09-27T03:34:40Z")

</div>

The certificate for [https://ecofriendlymamacanada.com/](https://ecofriendlymamacanada.com/) is self-signed from what I can tell. I’m not familiar with WP Encrypt, though, so you might want to ask the developer of that extension.

---

<div class="post-metadata">

**Author:** ![ecomamacanada](https://avatars.discourse-cdn.com/v4/letter/e/d9b06d/32.png) [@ecomamacanada](https://community.letsencrypt.org/u/ecomamacanada)\
**Post date:** [September 27, 2017, 3:39am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/5 "2017-09-27T03:39:28Z")

</div>

My apologies @ahaw021 I thought I did answer all those fields in my question

---

<div class="post-metadata">

**Author:** ![ecomamacanada](https://avatars.discourse-cdn.com/v4/letter/e/d9b06d/32.png) [@ecomamacanada](https://community.letsencrypt.org/u/ecomamacanada)\
**Post date:** [September 27, 2017, 3:55am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/6 "2017-09-27T03:55:08Z")

</div>

My domain is:

I ran this command: **clicked generate certificate**

It produced this output: **Challenge request failed for domain ecofriendlymamacanada.com1**

My web server is (include version): **Wordpress 4.8.2**

The operating system my web server runs on is (include version): **X 10.9.5**

My hosting provider, if applicable, is: **godaddy**

I can login to a root shell on my machine (yes or no, or I don’t know): **yes but they (go daddy) told me I shouldn’t**

I’m using a control panel to manage my site (no, or provide the name and version of the control panel): **Linux hosting with cPanel**

I hope this is all you need @ahaw021??

---

<div class="post-metadata">

**Author:** ![ecomamacanada](https://avatars.discourse-cdn.com/v4/letter/e/d9b06d/32.png) [@ecomamacanada](https://community.letsencrypt.org/u/ecomamacanada)\
**Post date:** [September 27, 2017, 3:59am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/7 "2017-09-27T03:59:43Z")

</div>

I didn’t pay for an SSL so I got a self assigned one @motoko. I’m trying to generate a .crt file that I can plug into my go daddy SSL certificate that I thought I was going to get through WP Encrypt (let’s encrypt via WP) and I can’t seem to get one. I don’t know what I need to do

---

<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:** [September 27, 2017, 5:14am UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/8 "2017-09-27T05:14:51Z")

</div>

The certificate has been issued successfully:

[https://crt.sh/?Identity=%ecofriendlymamacanada.com&iCAID=16418](https://crt.sh/?Identity=%25ecofriendlymamacanada.com&iCAID=16418)

So if it’s not correctly installed in your setup, I would suggest asking support for whoever seems most responsible (which might be GoDaddy—I’m not quite sure how to break down the responsibility here).

---

<div class="post-metadata">

**Author:** ![ecomamacanada](https://avatars.discourse-cdn.com/v4/letter/e/d9b06d/32.png) [@ecomamacanada](https://community.letsencrypt.org/u/ecomamacanada)\
**Post date:** [September 27, 2017, 2:50pm UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/9 "2017-09-27T14:50:46Z")

</div>

Thanks for your reply. I do see that I have a certificate but I was under the impression I had to have a .crt file to upload to my host. Godaddy sent me this article to help me but I’m not seeing a .crt file anywhere also I didn’t have to submit my CSR to let’s encrypt and from what I’m reading that’s what I needed to do as well. Is there something else I’m missing or another article I could read

 ![IMG_4189](https://global.discourse-cdn.com/letsencrypt/original/3X/8/a/8af884d758a2a09c7eb6b18d65361169f2e3569e.PNG)

---

<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:** [September 27, 2017, 5:53pm UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/10 "2017-09-27T17:53:35Z")

</div>

I'm not very familiar with WP Encrypt or GoDaddy, but...

> [@ecomamacanada](#):
>
> I do see that I have a certificate but I was under the impression I had to have a .crt file to upload to my host. Godaddy sent me this article to help me but I’m not seeing a .crt file anywhere

In the first post, you said you were "given 4 lines of certificate and key locations".

It's fairly common for certificates -- and private keys -- to have the general file extension ".pem", with names like "cert.pem" or "privkey.pem" to distinguish them.

If the documentation i've seen is correct, the certificate is in "`cert.pem`" and the private key is in "`private.pem`". The intermediate certificate is in "`chain.pem`", and "`fullchain.pem`" contains both `cert.pem` and `chain.pem` combined.

You probably need to give GoDaddy `private.pem` and either `fullchain.pem` or `cert.pem` and `chain.pem`.

> [@ecomamacanada](#):
>
> also I didn’t have to submit my CSR to let’s encrypt and from what I’m reading that’s what I needed to do as well

Let's Encrypt and the ACME protocol and clients are all about automation. When you clicked the button, your client generated a CSR and submitted it to Let's Encrypt using the API.

---

<div class="post-metadata">

**Author:** ![ecomamacanada](https://avatars.discourse-cdn.com/v4/letter/e/d9b06d/32.png) [@ecomamacanada](https://community.letsencrypt.org/u/ecomamacanada)\
**Post date:** [September 28, 2017, 8:13pm UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/11 "2017-09-28T20:13:40Z")

</div>

Thank you all problem has been solved!

---

<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:** [October 28, 2017, 8:14pm UTC](https://community.letsencrypt.org/t/challenge-request-failed-for-domain-ecofriendlymamacanada-com/43062/12 "2017-10-28T20:14:35Z")

</div>

Closed on October 28, 2017, 8:14pm UTC

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