mirror of
https://github.com/certimate-go/certimate.git
synced 2026-04-26 05:05:56 +03:00
[GH-ISSUE #949] v0.4.0 测试版 Bug 集中上报帖 / Pre-releases Bug Reports #650
Labels
No labels
announcement
backlog
bug
declined
documentation
duplicate
enhancement
good first issue
good first issue
help wanted
invalid
pull-request
question
stale
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/certimate#650
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @fudiwei on GitHub (Sep 3, 2025).
Original GitHub issue: https://github.com/certimate-go/certimate/issues/949
v0.4.0-alpha/beta/rc 预发布版本的 Bug 上报请在该 Issue 下方评论。
Please leave a comment to report bugs for v0.4.0-alpha/beta/rc pre-releases.
P.S. 仅供反馈 v0.4.0 测试版的 Bug，其他版本请单独开 Issue。反馈时请标注版本号、安装方式（全新安装 or 从旧版本升级）。
@JavaSCU commented on GitHub (Sep 4, 2025):
v0.4.0-alpha.3
使用工作流导出的配置，再次导入提示“节点 ID 无效：#-luacz_5ng5BIr7SzYPME”，感觉是旧版本生成的id有横杠开头，新版本校验不同，手工将-换成字母导入成功
"id": "-luacz_5ng5BIr7SzYPME",
{
"id": "6-ivm40m2kH1MVT69igva",
"type": "branchBlock",
"name": "分支 4",
"config": {},
"blocks": [
{
"id": "SqSiGsJEQmFvTfMFqhd_M",
"type": "tryCatch",
"name": "尝试执行…",
"blocks": [
{
"id": "tb9W1NZzHtofvI_xDBe_A",
"type": "tryBlock",
"name": "",
"blocks": [
{
"id": "-luacz_5ng5BIr7SzYPME",
"type": "bizDeploy",
"name": "部署证书-JC-ONLYOFFICE",
"config": {
"certificateOutputNodeId": "134e976189aa6d9ed005f",
"provider": "ssh",
"providerAccessId": "sf9h8sp84re63l7",
"providerConfig": {
"certPath": "/opt/onlyoffice/data/certs/onlyoffice.crt",
"format": "PEM",
"keyPath": "/opt/onlyoffice/data/certs/onlyoffice.key",
"postCommand": "docker restart onlyoffice\n"
},
"skipOnLastSucceeded": true
}
}
]
},
{
"id": "QDOs_QlB0UBiEG_oObWIV",
"type": "catchBlock",
"name": "若执行失败…",
"blocks": [
{
"id": "pTtTgFmZOGZl6DotodZ8I",
"type": "bizNotify",
"name": "推送通知",
"config": {
"channel": "webhook",
"message": "“部署证书-JC-ONLYOFFICE”出错",
"provider": "webhook",
"providerAccessId": "d4u1x3g532py7k6",
"providerConfig": {},
"subject": "paralleluniverse.fun-RSA2048"
}
},
{
"id": "n7hbog2llxigqi7",
"type": "end",
"name": "结束"
}
]
}
]
}
]
},
@JavaSCU commented on GitHub (Sep 4, 2025):
v0.4.0-alpha.3
在工作流列表界面，禁用某条工作流，刷新页面后，再次启用，提示“请先完成流程编排并发布更改”，此时该条工作流禁用后未进行过修改，进入编辑界面，“发布更改”按钮也为灰色不可用
@JavaSCU commented on GitHub (Sep 4, 2025):
v0.4.0-alpha.3
使用ACME自定义CA端点actalis服务失败，错误提示
[2025-09-04 11:24:12]acme config initialized
[2025-09-04 11:24:14]failed to initialize acme account
[2025-09-04 11:24:14]failed to register acme account: %!w()
@FarrelF commented on GitHub (Sep 4, 2025):
Is there a way to setup concurrency limit? I have scheduled workflow that expected to started at 08:00, but it not started until now (11:11 from here) due to concurrency limit.
The following is system logs from "Diagnostic" in "Settings":
@imlonghao commented on GitHub (Sep 4, 2025):
v0.4.0-alpha.3 版本使用需要
证书颁发机构授权的都会失败，只有类似 Let's Encrypt 这种才能成功@FarrelF commented on GitHub (Sep 4, 2025):
And, it seems that my scheduled workflows aren't started or getting "Pending" status for no clear reason, the system logs from "Diagnostic" in "Settings" page do not mention anything related to pending current running workflow, except for old task which is mentioned concurrency limit reason.
There is the screenshots:
The system log contents are as follows below:
The following screenshot is about cron jobs and workflow dispatcher:
@sunzhong2003 commented on GitHub (Sep 5, 2025):
v0.4.0-alpha.3 版本
1）向宝塔部署证书时，端口类型不正确
2）部署证书，希望有多个站点和端口，因为有可能部署十几个站点，端口还可能不同
@sunzhong2003 commented on GitHub (Sep 5, 2025):
是宝塔WAF网站哦
@imlonghao commented on GitHub (Sep 6, 2025):
0.4.0-alpha.4
终于看到了真正的错误提示，看起来这次的升级丢掉了之前的 ACME 账号，得重新申请配置 ACME EAB KID 和 ACME EAB HMAC Key 了
@Trashblazer commented on GitHub (Sep 6, 2025):
v0.3.26 迁移到 v0.4.0-alpha.4 工作流次序出现了错排。或者是我理解错了？你把try...catch的流程图放到了结点前面，看着不顺眼。
@fudiwei commented on GitHub (Sep 10, 2025):
@FarrelF
The default value of concurrency limit is up to your CPU numbers. You can control it through the environment variable.
But I have no idea why your workflow is hanging. Could you please upgrade to
v0.4.0-alpha.5? I added some system log outputs, may be helpful for debugging.@fudiwei commented on GitHub (Sep 10, 2025):
@imlonghao
我无法复现 ACME 账号丢失的这个问题。你还有 v0.3.x 的数据备份吗？如果有，请尝试使用数据库工具打开程序根目录下的
/pb_data/data.db，这是一个 SQLite 数据库。麻烦看一下acme_accounts这张表，ACME 账号数据是否正确的迁移？如果可能的话，请贴出升级前、后的两张表的完整数据来帮助我定位问题（私钥字段内容切记脱敏）。@imlonghao commented on GitHub (Sep 11, 2025):
时间有点长，没有 0.3.x 的备份了，我观察到目前我的
acme_accounts里， 有问题的这个 ACME 账号的 acmeDirUrl 是空的我是一路升级上来的，您试试按照我的这个路径能不能复现？
0.3.26 -> 0.4.0-alpha.1 -> 0.4.0-alpha.3 -> 0.4.0-alpha.4
@FarrelF commented on GitHub (Sep 11, 2025):
@fudiwei I updated the Certimate to
v0.4.0-alpha.5and some of my scheduled workflow still hanging, the system logs in "Diagnostic" mentioned concurrency limit reason, but the workflow still not running from expected run time (at 18:00) until now.This happens if I set same cron jobs in all of my workflows (which is
0 */2 * * *), I'm never had this issue yet when I set different cron job in every single workflow.There is a screenshots for pending running workflow:
The system log contents are as follows below:
The following screenshot is about my current cron jobs and workflow dispatcher:
I tried set and export the
CERTIMATE_WORKFLOW_MAX_WORKERSto16before start the Certimate, but when I started it seems that maximum concurrency limit still at 2 and the "Concurrency" on Workflow Dispatcher still shows 2 as you can see the screenshot above.There is the latest log:
@LTK3 commented on GitHub (Sep 13, 2025):
docker 部署发现 会一直跑满一个核心.不知道是否为正常行为.
@fudiwei commented on GitHub (Sep 13, 2025):
@LTK3
是哪一个版本呢？另外麻烦贴下机器配置。
@Trashblazer commented on GitHub (Sep 13, 2025):
系统设置里，初始显示 zh-CN，呈现效果不统一
选择简体中文保存后显示简体中文
@LTK3 commented on GitHub (Sep 13, 2025):
重新拉取了最新的rc1 已恢复正常
@imlonghao commented on GitHub (Sep 19, 2025):
v0.4.0-rc.1 使用条件分支时会失败，下面的工作流会在监控节点之后直接失败
@SiLong96 commented on GitHub (Sep 22, 2025):
条件分支无法运行
@Muione commented on GitHub (Sep 25, 2025):
v0.4.0-rc.2
当不存在过期证书时，点击已过期会提示“请求错误 Something went wrong.”
@huaizhengu commented on GitHub (Sep 26, 2025):
在使用ucloud的DNS服务器时,出现报错 time="2025-09-26T10:28:33+08:00" level=warning msg="[8109d542-1ee9-43e9-914f-cb7d488095d0] do UdnrDomainDNSQuery failed, api:\n[server.RetCodeError] 299 IAM permission error"
经过排查,是由于请求时 缺少 Project_id
@fudiwei commented on GitHub (Sep 27, 2025):
@Muione 无法复现。浏览器开发者工具里有其他错误信息吗？