[英]Repeated 'Too many certificates already issued for exact set of domains' error with GreenLock package
I have already checked this post .我已经检查过这篇文章。 But even though I tried that method, it didn't work, so I open a new issue.但是即使我尝试了那个方法,它也没有用,所以我打开了一个新的问题。
I use AWS EC2 server and deploy with aws pipeline.我使用 AWS EC2 服务器并使用 aws 管道进行部署。 So When I push to github repository, it will automatically build and deploy to production server.所以当我推送到 github 存储库时,它会自动构建并部署到生产服务器。
At first it's works fine, and there are no errors in the console.起初它工作正常,并且控制台中没有错误。
But one day an error began to occur.但是有一天,错误开始发生。 So when I checked the console, there was an error as below.所以当我检查控制台时,出现如下错误。
[Error Message in console] [控制台中的错误消息]
set greenlockOptions.notify to override the default logger
certificate_order (more info available: account subject altnames challengeTypes)
Error cert_issue:
[acme-v2.js] authorizations were not fetched for 'mydomain.com':
{"type":"urn:ietf:params:acme:error:rateLimited","detail":"Error creating new order :: too many certificates already issued for exact set of domains: mydomain.com: see https://letsencrypt.org/docs/rate-limits/","status":429,"_identifiers":[{"type":"dns","value":"mydomain.com"}]}
Error: [acme-v2.js] authorizations were not fetched for 'mydomain.com':
{"type":"urn:ietf:params:acme:error:rateLimited","detail":"Error creating new order :: too many certificates already issued for exact set of domains: mydomain.com: see https://letsencrypt.org/docs/rate-limits/","status":429,"_identifiers":[{"type":"dns","value":"mydomain.com"}]}
at Object.E.NO_AUTHORIZATIONS (/home/project/build/node_modules/@root/acme/errors.js:75:9)
at /home/project/build/node_modules/@root/acme/acme.js:1198:11
at processTicksAndRejections (internal/process/task_queues.js:97:5)
Error cert_issue:
[acme-v2.js] authorizations were not fetched for 'mydomain.com':
In my opinion, I think there was a limit to the process of reissuing the certificate every time I push the code, but I don't know where the problem occurred even if I check the code.在我看来,我觉得每次push代码的时候重新颁发证书的过程是有限制的,但是我查了代码也不知道是哪里出了问题。
My code structure is written as below and developed with Express.我的代码结构如下所示,是用 Express 开发的。
[server.js] [服务器.js]
"use strict";
const app = require("./app.js");
require("greenlock-express")
.init({
packageRoot: __dirname,
configDir: "./greenlock.d",
// contact for security and critical bug notices
maintainerEmail: process.env.EMAIL,
// whether or not to run at cloudscale
cluster: false
})
// Serves on 80 and 443
// Get's SSL certificates magically!
.serve(app);
[greenlock.d/config.json] [greenlock.d/config.json]
{ "sites": [{ "subject": "mydomain.com", "altnames": ["mydomain.com"] }] }
[.greenlockrc] [.greenlockrc]
{"configDir":"./greenlock.d"}
[package.json (scripts.start line)] [package.json(scripts.start 行)]
"scripts": {
"start": "node server.js"
},
I am aware of the seven-day limit from Let's Encrypt.我知道 Let's Encrypt 的 7 天限制。 So I want to find a way to solve this problem.所以我想找到一种方法来解决这个问题。
in my express folder, I do在我的快递文件夹里,我做
sudo chmod 775 ./greenlock.d
then I delete greenlock.d(one time) and npm start然后我删除 greenlock.d(一次)和 npm 开始
I dont have issue since我没有问题因为
声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.