Hello Mr. Matt,
It’s still not generated RSA key file instead of EC key, even though I added below code to my Caddyfile.
tls {
key_type rsa2048
}
And my Caddyfile is now as below…
mydomain.com
{
reverse_proxy 127.0.0.1:5000`
}
tls {
key_type rsa2048
}
Please help me. Thank you in advance!
1. Caddy version (caddy version
):
2. How I run Caddy:
a. System environment:
b. Command:
Paste command here.
c. Service/unit/compose file:
Paste full file contents here.
Make sure backticks stay on their own lines,
and the post looks nice in the preview pane.
d. My complete Caddyfile or JSON config:
{
"sans": [
"mydomain.com"
],
"issuer_data": {
"url": "https://acme-v02.api.letsencrypt.org/acme/cert/04---aee8f5-----a3e83c--acafbf5"
}
}
Paste config here, replacing this text.
Use caddy fmt
to make it readable.
DO NOT REDACT anything except credentials.
LEAVE DOMAIN NAMES INTACT.
Make sure the backticks stay on their own lines.
### 3. The problem I'm having:
<!-- What are you trying to do, and what isn't working? Please describe the issue thoroughly enough so that anyone can reproduce the exact behavior you're seeing. Be as specific as possible. DO NOT USE WEB BROWSERS; use "curl -v" instead. -->
-----BEGIN EC PRIVATE KEY-----
MHcCAQEEIMnb5yhMoHQkhZlglH94c2wLE9SBh2YX+MaK76lx+3/YoAoGCCqGSM4
### 4. Error messages and/or full log output:
<!-- Please **DO NOT REDACT** any information except credentials. Leave domain names intact! -->
<!-- Please **DO NOT POST TRUNCATED LOG LINES** as systemd is notorious for this. -->
<!-- Please **DO NOT USE WEB BROWSERS.** Use curl -v instead. -->
<!-- Please **DO ENABLE DEBUG MODE FIRST** by adding "debug" to the global options of your Caddyfile. -->
### 5. What I already tried:
<!-- Show us what effort you've put in to solving the problem. Be specific -- people are volunteering their time to help you! Low effort posts are not likely to get good answers! -->
### 6. Links to relevant resources: