简体   繁体   English

cert-manager:让我们加密拒绝 ACME 帐户

[英]cert-manager: let's encrypt refuses ACME account

I followed the cert-manager tutorial to enable tls in my k3s cluster .我按照cert-manager 教程在我的k3s 集群中启用了 tls。 So I modified the letsencrypt-staging issuer file to look like this:所以我修改了letsencrypt-staging issuer文件,如下所示:

apiVersion: cert-manager.io/v1
kind: ClusterIssuer
metadata:
    name: letsencrypt-staging
spec:
    acme:
        # The ACME server URL
        server: https://acme-staging-v02.api.letsencrypt.org/directory
        # Email address used for ACME registration
        email: mail@example.com
        # Name of a secret used to store the ACME account private key
        privateKeySecretRef:
            name: letsencrypt-staging
        # Enable the HTTP-01 challenge provider
        solvers:
        - http01:
            ingress:
                class: traefik

but when I deploy it, I get the error Failed to verify ACME account: Get "https://acme-staging-v02.api.letsencrypt.org/directory": read tcp 10.42.0.96:45732->172.65.46.172:443: read: connection reset by peer .但是当我部署它时,我收到错误Failed to verify ACME account: Get "https://acme-staging-v02.api.letsencrypt.org/directory": read tcp 10.42.0.96:45732->172.65.46.172:443: read: connection reset by peer But thats only with the staging clusterIssuer.但这仅适用于 staging clusterIssuer。 The production example from te tutorial works flawlessly. te教程中的生产示例完美无缺。 I resacherd this error and it seems to be somthing with the kubernetes dns but I don't know how to test the dns or any other way to figure this error out.我重新发现了这个错误,它似乎与 kubernetes dns 有关,但我不知道如何测试 dns 或任何其他方法来解决这个错误。


Tested the kubernetes DNS and it is up and running, so it must be an error with cert-manager,especially because the prod certificates status says `Ready=True测试了 kubernetes DNS 并且它已启动并正在运行,所以它一定是 cert-manager 的错误,特别是因为prod证书状态显示 `Ready=True

So it seems like I ran into a let's encrypt limit.所以看起来我遇到了让我们加密的限制。 After waiting for a day, the certificate now works等了一天,证书现在可以用了

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 在 Kubernetes 和 nginx 入口上使用客户端证书身份验证时,如何修复 cert-manager 对 Let's Encrypt ACME 挑战的响应? - How to fix cert-manager responses to Let's Encrypt ACME challenges when using client certificate authentication on Kubernetes with nginx ingress? Kubernetes让加密证书管理器找不到错误密码 - Kubernetes Let's Encrypt cert-manager Error secret not found k8s 无法使用 cert-manager 为 GoDaddy 域生成 Let's Encrypt 证书 - k8s Unable to generate Let's Encrypt Certificates for GoDaddy Domains using cert-manager 如何在裸机集群上使用cert-manager自动在Kubernetes中加密证书更新? - How to automate Let's Encrypt certificate renewal in Kubernetes with cert-manager on a bare-metal cluster? 通配符让我们使用 cert-manager、nginx 入口、kubernetes 中的 cloudflare 加密证书如何解决? - Wildcard Let's Encrypt certificates with cert-manager, nginx ingress, cloudflare in kubernetes how to fix? 证书管理器在升级到 AKS 1.20.7 后停止更新 Let'S Encrypt 证书 - Cert-manager stopped renewing Let'S Encrypt certificates after upgrading to AKS 1.20.7 如何使用来自 Let's Encrypt 的通配符证书和 cert-manager - How to use Wildcard certificates from Let’s Encrypt with cert-manager 使用Cert-Manager,NGINX Ingress和Let's Encrypt为Kubernetes服务配置TLS / SSL - Configure TLS/SSL for Kubernetes Services using Cert-Manager, NGINX Ingress and Let’s Encrypt SSL 证书来自 Let's Encrypt 在您的 Kubernetes Ingress via cert-manager - SSL certificates from Let’s Encrypt in your Kubernetes Ingress via cert-manager 证书管理器:让我们用 nginx 加密 HTTP01 挑战(没有入口) - cert-manager: Let's Encrypt HTTP01 challenge with nginx (without ingress)
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM