# Help with WP Encrypt plugin on Wordpress

**URL:** <https://community.letsencrypt.org/t/help-with-wp-encrypt-plugin-on-wordpress/82907>\
**Category:** Help\
**Created:** [January 18, 2019, 9:18am UTC](https://community.letsencrypt.org/t/help-with-wp-encrypt-plugin-on-wordpress/82907 "2019-01-18T09:18:41Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Receptie](https://avatars.discourse-cdn.com/v4/letter/r/5f8ce5/32.png) [@Receptie](https://community.letsencrypt.org/u/Receptie)\
**Post date:** [January 18, 2019, 9:18am UTC](https://community.letsencrypt.org/t/help-with-wp-encrypt-plugin-on-wordpress/82907/1 "2019-01-18T09:18:41Z")

</div>

My domain is: www.bastiaensgroup.nl

And I am trying to get the WP Encrypt plugin to work. I filled in the account settings and clicked on the ‘register account’ button to get an account on Let’s Encrypt.  
The help feature tells me that a new button should appear, namely the ‘generate SSL’ button. However, it didn’t. No matter how many times I push the ‘register account’ button. I can’t seem to find a solution anywhere. Can someone help me?

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [January 18, 2019, 9:59am UTC](https://community.letsencrypt.org/t/help-with-wp-encrypt-plugin-on-wordpress/82907/2 "2019-01-18T09:59:15Z")

</div>

Hi @Receptie

> [@Receptie](#):
>
> www.bastiaensgroup.nl

you have an ipv4 and an ipv6 - address ( [https://check-your-website.server-daten.de/?q=bastiaensgroup.nl](https://check-your-website.server-daten.de/?q=bastiaensgroup.nl) ):

| Host | T | IP-Address | is auth. | ∑ Queries | ∑ Timeout |
| --- | --- | --- | --- | --- | --- |
| bastiaensgroup.nl | A | 81.169.145.105 | yes | 2 | 0 |
| | AAAA | 2A01:0238:020A:0202:1105:0000:0000:0000 | yes | | |
| www.bastiaensgroup.nl | C | bastiaensgroup.nl | yes | 1 | 0 |
| | A | 81.169.145.105 | yes | | |

May be a problem because ipv6 isn't configured correct.

And checking /.well-known/acme-challenge there is a critical answer:

| Domainname | Http-Status | redirect | Sec. | G |
| --- | --- | --- | --- | --- |
| • [http://www.bastiaensgroup.nl/](http://www.bastiaensgroup.nl/) | | | | |
| 81.169.145.105 | 301 | [http://bastiaensgroup.nl/](http://bastiaensgroup.nl/) | 0.310 | D |
| | | | | |
| • [http://bastiaensgroup.nl/](http://bastiaensgroup.nl/) | | | | |
| 81.169.145.105 | 200 | | 0.973 | H |
| | | | | |
| • [https://bastiaensgroup.nl/](https://bastiaensgroup.nl/) | | | | |
| 81.169.145.105 | -10 | | 0.040 | P |
| SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel. | | | | |
| | | | | |
| • [https://www.bastiaensgroup.nl/](https://www.bastiaensgroup.nl/) | | | | |
| 81.169.145.105 | -10 | | 0.040 | P |
| SecureChannelFailure - The request was aborted: Could not create SSL/TLS secure channel. | | | | |
| | | | | |
| • [http://www.bastiaensgroup.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://www.bastiaensgroup.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | |
| 81.169.145.105 | 301 | [http://bastiaensgroup.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://bastiaensgroup.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | 0.276 | D |
| | | | | |
| • [http://bastiaensgroup.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://bastiaensgroup.nl/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | |
| 81.169.145.105 | -8 | | 0.380 | W |
| ConnectionClosed - The request was aborted: The connection was closed unexpectedly. | | | | |

The "ConnectionClosed" is bad.

Looks like the WP plugin doesn't understand your configuration.

---

<div class="post-metadata">

**Author:** ![Receptie](https://avatars.discourse-cdn.com/v4/letter/r/5f8ce5/32.png) [@Receptie](https://community.letsencrypt.org/u/Receptie)\
**Post date:** [January 18, 2019, 10:19am UTC](https://community.letsencrypt.org/t/help-with-wp-encrypt-plugin-on-wordpress/82907/3 "2019-01-18T10:19:12Z")

</div>

Okay…Any idea how I can solve it?

---

<div class="post-metadata">

**Author:** ![JuergenAuer](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/juergenauer/32/26491_2.png) [@JuergenAuer](https://community.letsencrypt.org/u/JuergenAuer)\
**Post date:** [January 18, 2019, 10:31am UTC](https://community.letsencrypt.org/t/help-with-wp-encrypt-plugin-on-wordpress/82907/4 "2019-01-18T10:31:59Z")

</div>

> [@Receptie](#):
>
> Any idea how I can solve it?

Such tools are "closed worlds", so it's nearly impossible.

Check if it works if you remove temporarily your ipv6 address.

It's possible that the blocked /.well-known/acme-challenge is from this tool - \> no problem.

Not from this tool -\> big problem.

---

<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:** [February 17, 2019, 10:32am UTC](https://community.letsencrypt.org/t/help-with-wp-encrypt-plugin-on-wordpress/82907/5 "2019-02-17T10:32:11Z")

</div>

Closed on February 17, 2019, 10:32am UTC

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