# Error issuing certificate

**URL:** <https://community.letsencrypt.org/t/error-issuing-certificate/147601>\
**Category:** Help\
**Created:** [March 16, 2021, 8:44pm UTC](https://community.letsencrypt.org/t/error-issuing-certificate/147601 "2021-03-16T20:44:32Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![arraddir](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@arraddir](https://community.letsencrypt.org/u/arraddir)\
**Post date:** [March 16, 2021, 8:44pm UTC](https://community.letsencrypt.org/t/error-issuing-certificate/147601/1 "2021-03-16T20:44:32Z")

</div>

Hi. im having problem with issuing certificate. i deleted old one idont know why(!) trying to issue again but it gives me this error.  
There was a problem processing your request

- Error issuing certificate
- Failed to issue certificate
- Updating challenge for [mail.makopcowmats.com](http://mail.makopcowmats.com): acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from [http://mail.makopcowmats.com/.well-known/acme-challenge/cYeTsqIgM2AyiCni-RQ9\_FbcIi78qyg6ZFWti0uYZy0](http://mail.makopcowmats.com/.well-known/acme-challenge/cYeTsqIgM2AyiCni-RQ9_FbcIi78qyg6ZFWti0uYZy0) [45.84.191.3]: "\<html lang="en-US" charset="UTF-8"\> \<meta charset="UTF-8"\>\<meta http-equiv="refresh" content="1" /\>\<meta http-equiv="cache" (order URL: [https://acme-staging-v02.api.letsencrypt.org/acme/order/18609247/10784927](https://acme-staging-v02.api.letsencrypt.org/acme/order/18609247/10784927))

My domain is: [makopcowmats.com](http://makopcowmats.com)

I ran this command: issuing certificate

It produced this output: \* Error issuing certificate

- Failed to issue certificate
- Updating challenge for [mail.makopcowmats.com](http://mail.makopcowmats.com/): acme: error code 403 "urn:ietf:params:acme:error:unauthorized": Invalid response from [http://mail.makopcowmats.com/.well-known/acme-challenge/cYeTsqIgM2AyiCni-RQ9\_FbcIi78qyg6ZFWti0uYZy0](http://mail.makopcowmats.com/.well-known/acme-challenge/cYeTsqIgM2AyiCni-RQ9_FbcIi78qyg6ZFWti0uYZy0) [45.84.191.3]: " \<meta http-equiv="cache" (order URL: [https://acme-staging-v02.api.letsencrypt.org/acme/order/18609247/10784927](https://acme-staging-v02.api.letsencrypt.org/acme/order/18609247/10784927))

My web server is (include version): apache 2.4.46

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

My hosting provider, if applicable, is: guzelhosting

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

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

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): not sure

---

<div class="post-metadata">

**Author:** ![Osiris](https://avatars.discourse-cdn.com/v4/letter/o/839c29/32.png) [@Osiris](https://community.letsencrypt.org/u/Osiris)\
**Post date:** [March 16, 2021, 8:49pm UTC](https://community.letsencrypt.org/t/error-issuing-certificate/147601/2 "2021-03-16T20:49:44Z")

</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. [crt.sh | 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):

The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot):

---

<div class="post-metadata">

**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\
**Post date:** [March 16, 2021, 9:02pm UTC](https://community.letsencrypt.org/t/error-issuing-certificate/147601/3 "2021-03-16T21:02:30Z")

</div>

Welcome to the Let's Encrypt Community 🙂

In addition to what @Osiris mentioned...

Requesting `http://mail.makopcowmats.com/.well-known/acme-challenge/test` yields a response from an nginx webserver with an application redirect to `https://mail.makopcowmats.com/.well-known/acme-challenge/test` that yields a response from a LiteSpeed webserver.

With this configuration, I'm very curious as to how you're trying to fulfill an http-01 challenge.

> **[Challenge Types - Let's Encrypt - Free SSL/TLS Certificates](https://letsencrypt.org/docs/challenge-types/)**
>
> Last updated: Dec 8, 2020 | See all Documentation When you get a certificate from Let’s Encrypt, our servers validate that you control the domain names in that certificate using “challenges,” as defined by the ACME standard. Most of the time, this...

---

<div class="post-metadata">

**Author:** ![arraddir](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@arraddir](https://community.letsencrypt.org/u/arraddir)\
**Post date:** [March 16, 2021, 9:33pm UTC](https://community.letsencrypt.org/t/error-issuing-certificate/147601/4 "2021-03-16T21:33:32Z")

</div>

it was my first website project with wordpress. So i dont get what exactly you are saying.

---

<div class="post-metadata">

**Author:** ![\_az](https://avatars.discourse-cdn.com/v4/letter/_/22d042/32.png) [@\_az](https://community.letsencrypt.org/u/_az)\
**Post date:** [March 16, 2021, 9:43pm UTC](https://community.letsencrypt.org/t/error-issuing-certificate/147601/5 "2021-03-16T21:43:14Z")

</div>

Hi @arraddir,

Could you please check whether you have [Force HTTPS Redirect](https://blog.cpanel.com/force-https-redirection/) enabled inside cPanel?

It's possible that the redirect might be coming from your `.htaccess` file or from a WordPress plugin as well.

I would guess that the problem is that the forced redirect is causing the certificate issuing process to fail, because the redirection is ending up on a different customer's domain (`dryplatin.com`) due to you not having a certificate yet.

The solution here would be to temporarily remove the HTTPS redirect, and then try issue the certificate.

Once you have a certificate, you can enable the redirect again.

---

<div class="post-metadata">

**Author:** ![arraddir](https://avatars.discourse-cdn.com/v4/letter/a/7cd45c/32.png) [@arraddir](https://community.letsencrypt.org/u/arraddir)\
**Post date:** [March 16, 2021, 10:07pm UTC](https://community.letsencrypt.org/t/error-issuing-certificate/147601/6 "2021-03-16T22:07:46Z")

</div>

Thank you it worked.

---

<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 15, 2021, 10:08pm UTC](https://community.letsencrypt.org/t/error-issuing-certificate/147601/7 "2021-04-15T22:08:27Z")

</div>

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