# 140602:Expecting: ANY PRIVATE KEY

**URL:** <https://community.letsencrypt.org/t/140602-any-private-key/145230>\
**Category:** Help\
**Created:** [February 14, 2021, 2:54am UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230 "2021-02-14T02:54:20Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![pineapplejoe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pineapplejoe/32/36385_2.png) [@pineapplejoe](https://community.letsencrypt.org/u/pineapplejoe)\
**Post date:** [February 14, 2021, 2:54am UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230/1 "2021-02-14T02:54:20Z")

</div>

So I am trying to get two domains registered and im hitting this problem.

Command I run (as su):  
./acme.sh --issue -d staging.flutter.tours -d [karmagrade.com](http://karmagrade.com) -w /usr/share/nginx/html --force --debug

Output:  
[Sun Feb 14 02:50:11 UTC 2021] Multi domain='DNS:staging.flutter.tours,DNS:karmagrade.com'

unable to load Private Key

140602583942992:error:0906D06C:PEM routines:PEM\_read\_bio:no start line:pem\_lib.c:707:Expecting: ANY PRIVATE KEY

[Sun Feb 14 02:50:11 UTC 2021] **Create CSR error.**

[Sun Feb 14 02:50:11 UTC 2021] pid

[Sun Feb 14 02:50:11 UTC 2021] No need to restore nginx, skip.

[Sun Feb 14 02:50:11 UTC 2021] \_clearupdns

[Sun Feb 14 02:50:11 UTC 2021] dns\_entries

[Sun Feb 14 02:50:11 UTC 2021] skip dns.

[Sun Feb 14 02:50:11 UTC 2021] \_on\_issue\_err

[Sun Feb 14 02:50:11 UTC 2021] **Please add '--debug' or '--log' to check more details.**

[Sun Feb 14 02:50:11 UTC 2021] **See: [How to debug acme.sh · acmesh-official/acme.sh Wiki · GitHub](https://github.com/acmesh-official/acme.sh/wiki/How-to-debug-acme.sh)**

I've read the other "private key" topics ... and I dont get them either LOL.

What am I missing?

---

<div class="post-metadata">

**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\
**Post date:** [February 14, 2021, 4:04am UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230/2 "2021-02-14T04:04:45Z")

</div>

First: Using `--force` is kind of a _last resort_; I don't see how adding that to the command above improves your situation.  
[you can't force it to read the private key]

Let's have a look at which certs are currently maintained by `acme.sh` with:  
`./acme.sh --list`

---

<div class="post-metadata">

**Author:** ![pineapplejoe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pineapplejoe/32/36385_2.png) [@pineapplejoe](https://community.letsencrypt.org/u/pineapplejoe)\
**Post date:** [February 17, 2021, 4:44pm UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230/3 "2021-02-17T16:44:45Z")

</div>

This is what I see with --list

Main\_Domain KeyLength SAN\_Domains CA Created Renew  
[karmagrade.com](http://karmagrade.com) "" no [LetsEncrypt.org](http://LetsEncrypt.org)  
staging.flutter.tours "" [karmagrade.com](http://karmagrade.com)[LetsEncrypt.org](http://LetsEncrypt.org) Sat Feb 13 03:14:48 UTC 2021 Wed Apr 14 03:14:48 UTC 2021

---

<div class="post-metadata">

**Author:** ![webprofusion](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/webprofusion/32/85310_2.png) [@webprofusion](https://community.letsencrypt.org/u/webprofusion)\
**Post date:** [February 18, 2021, 3:39am UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230/4 "2021-02-18T03:39:18Z")

</div>

Your private key file is missing or not accessible?

Check in the path where your cert file for this domain is kept (as per your nginx cert config).

If the private .key file is indeed missing I wonder if you might be best to remove this configuration and start again, alternatively create a new private key file (look where the rest of your cert files are being created) or copy a different one.

---

<div class="post-metadata">

**Author:** ![pineapplejoe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pineapplejoe/32/36385_2.png) [@pineapplejoe](https://community.letsencrypt.org/u/pineapplejoe)\
**Post date:** [March 3, 2021, 10:26pm UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230/5 "2021-03-03T22:26:15Z")

</div>

Thanks. How do I remove the configuration exactly?

---

<div class="post-metadata">

**Author:** ![pineapplejoe](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/pineapplejoe/32/36385_2.png) [@pineapplejoe](https://community.letsencrypt.org/u/pineapplejoe)\
**Post date:** [March 4, 2021, 1:31am UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230/6 "2021-03-04T01:31:21Z")

</div>

Figured it out.  
just removed ~/.acme.sh/ and started again.

---

<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 4, 2021, 6:41pm UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230/7 "2021-03-04T18:41:35Z")

</div>

> [@pineapplejoe](#):
>
> just removed ~/.acme.sh/ and started again.

Please make note of the rate limits applicable if you haven't done so already: [Rate Limits - Let's Encrypt](https://letsencrypt.org/docs/rate-limits/)

It might not be relevant in this specific case, but removing previously issued certificates carelessly by removing entire directories from an ACME client, such as in this case, might lead to rate limit issues. I'm not saying you'd do that in the future, but I thought it might be a good idea to warn you and/or other people finding this thread anyway 🙂

---

<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 3, 2021, 6:41pm UTC](https://community.letsencrypt.org/t/140602-any-private-key/145230/8 "2021-04-03T18:41:48Z")

</div>

Closed on April 3, 2021, 6:41pm UTC

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