# Certificate not activating **URL:** \ **Category:** Help\ **Created:** [July 18, 2019, 8:22am UTC](https://community.letsencrypt.org/t/certificate-not-activating/98076 "2019-07-18T08:22:29Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![marketon](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@marketon](https://community.letsencrypt.org/u/marketon)\ **Post date:** [July 18, 2019, 8:22am UTC](https://community.letsencrypt.org/t/certificate-not-activating/98076/1 "2019-07-18T08:22:29Z")
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: [http://polaarenergy.com](http://polaarenergy.com) I ran this command: trying to install certificate from Plesk. It produced this output: Error: Could not issue a Let’s Encrypt SSL/TLS certificate for **[polaarenergy.com](http://polaarenergy.com)**. The authorization token is not available at [http://polaarenergy.com/.well-known/acme-challenge/svC1HIVtS0I7FKmZiA72zGu5lGMobBV3v5xD\_7-jWp0](http://polaarenergy.com/.well-known/acme-challenge/svC1HIVtS0I7FKmZiA72zGu5lGMobBV3v5xD_7-jWp0). To resolve the issue, make sure that the token file can be downloaded via the above URL. [See the related Knowledge Base article for details.](https://support.plesk.com/hc/en-us/articles/115000165013) Details Invalid response from [https://acme-v02.api.letsencrypt.org/acme/authz/sdh9iz89j2pAaKKUjC1GiPfExoic\_s3f\_hEq0m\_SL3Q](https://acme-v02.api.letsencrypt.org/acme/authz/sdh9iz89j2pAaKKUjC1GiPfExoic_s3f_hEq0m_SL3Q). Details: Type: urn:ietf:params:acme:error:unauthorized Status: 403 Detail: Invalid response from [http://polaarenergy.com/.well-known/acme-challenge/svC1HIVtS0I7FKmZiA72zGu5lGMobBV3v5xD\_7-jWp0](http://polaarenergy.com/.well-known/acme-challenge/svC1HIVtS0I7FKmZiA72zGu5lGMobBV3v5xD_7-jWp0) [109.238.10.122]: “\n\n404 Not Found\n\n # Not Found \n\ **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:** [July 18, 2019, 8:53am UTC](https://community.letsencrypt.org/t/certificate-not-activating/98076/2 "2019-07-18T08:53:14Z") Hi @marketon > [@marketon](#): > > My domain is: [http://polaarenergy.com](http://polaarenergy.com) checking your domain via [https://check-your-website.server-daten.de/?q=polaarenergy.com](https://check-your-website.server-daten.de/?q=polaarenergy.com) there is no error visible. | Domainname | Http-Status | redirect | Sec. | G | | --- | --- | --- | --- | --- | | • [http://polaarenergy.com/](http://polaarenergy.com/) | | | | | | 109.238.10.122 | 200 | | 0.070 | H | | | | | | | | • [http://www.polaarenergy.com/](http://www.polaarenergy.com/) | | | | | | 109.238.10.122 | 200 | | 0.074 | H | | | | | | | | • [https://polaarenergy.com/](https://polaarenergy.com/) | | | | | | 109.238.10.122 | -4 | | 0.124 | W | | SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format. | | | | | | | | | | | | • [https://www.polaarenergy.com/](https://www.polaarenergy.com/) | | | | | | 109.238.10.122 | -4 | | 0.483 | W | | SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format. | | | | | | | | | | | | • [http://polaarenergy.com:443/](http://polaarenergy.com:443/) | | | | | | 109.238.10.122 | 200 | | 0.077 | Q | | | | | | | | • [http://www.polaarenergy.com:443/](http://www.polaarenergy.com:443/) | | | | | | 109.238.10.122 | 200 | | 0.070 | Q | | | | | | | | • [http://polaarenergy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://polaarenergy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | | | 109.238.10.122 | 404 | | 0.066 | A | | Not Found | | | | | | Visible Content: Not Found The requested URL /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de was not found on this server. Apache Server at [polaarenergy.com](http://polaarenergy.com) Port 80 | | | | | | | | | | | | • [http://www.polaarenergy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de](http://www.polaarenergy.com/.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de) | | | | | | 109.238.10.122 | 404 | | 0.067 | A | | Not Found | | | | | | Visible Content: Not Found The requested URL /.well-known/acme-challenge/check-your-website-dot-server-daten-dot-de was not found on this server. Apache Server at [www.polaarenergy.com](http://www.polaarenergy.com) Port 80 | | | | | The /.well-known/acme-challenge/random-filename answers with the expected http status 404 - Not Found. But: Plesk is a closed world. So it should work. If it doesn't work -\> ask your hoster. One thing is curious: Your http + / sends: > X-Powered-By: PleskLin But /.well-known/acme-challenge doesn't send that header, instead, there is the standard Apache "Not Found" message. Do you have added additional definitions Plesk doesn't understand? Or your hoster catches /.well-known/acme-challenge, so this Plesk-Header isn't sent. ---
**Author:** ![marketon](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@marketon](https://community.letsencrypt.org/u/marketon)\ **Post date:** [July 18, 2019, 9:09am UTC](https://community.letsencrypt.org/t/certificate-not-activating/98076/3 "2019-07-18T09:09:58Z")
> [@JuergenAuer](#): > > The /.well-known/acme-challenge/random-filename answers with the expected http status 404 - Not Found. > > But: Plesk is a closed world. So it should work. > > If it doesn’t work -\> ask your hoster. > > One thing is curious: Your http + / sends: > > > X-Powered-By: PleskLin > > But /.well-known/acme-challenge doesn’t send that header, instead, there is the standard Apache “Not Found” message. > > Do you have added additional definitions Plesk doesn’t understand? > > Or your hoster catches /.well-known/acme-challenge, so this Plesk-Header isn’t sent. Thanks for the fast reply. So basically I need to contact the hosting company. Nothing to do for me? ---
**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:** [July 18, 2019, 9:45am UTC](https://community.letsencrypt.org/t/certificate-not-activating/98076/4 "2019-07-18T09:45:46Z")
> [@marketon](#): > > So basically I need to contact the hosting company. Nothing to do for me? Yes, ask your hoster. Plesk -\> closed world. And check the list: [https://support.plesk.com/hc/en-us/articles/115000165013](https://support.plesk.com/hc/en-us/articles/115000165013) > If the server contains custom rewrite rules, disable them by renaming `.htaccess` file or `web.config` . Also, remove custom rewrite rules from **Plesk \> Domains \> [example.com](http://example.com) \> Apache & nginx settings**. and > Make sure that the **Run the website in compatibility mode for the legacy option "Separate SSL/TLS and non-SSL/TLS content Plesk \> Domains \> [example.com](http://example.com) \> DNS Settings** option is not enabled in **Plesk \> Tools & Settings \> Domains \> [example.com](http://example.com) \> Hosting Settings** looks critical. ---
**Author:** ![marketon](https://avatars.discourse-cdn.com/v4/letter/m/90ced4/32.png) [@marketon](https://community.letsencrypt.org/u/marketon)\ **Post date:** [July 18, 2019, 2:04pm UTC](https://community.letsencrypt.org/t/certificate-not-activating/98076/5 "2019-07-18T14:04:47Z")
Thanks a lot! I’ve contacted them and now the problem is solved! ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [August 17, 2019, 2:04pm UTC](https://community.letsencrypt.org/t/certificate-not-activating/98076/6 "2019-08-17T14:04:55Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.