1Panel-dev / 1Panel-dev/1Panel

[Feature] Add a stop button when applying for a certificate

Open
#13,151 2 comments 0 reactions 1 assignee View on GitHub

@wanghe-fit2cloud is already working on this.

Since Jun 30, 2026.

type: feature-request
Dominant language
Go
Stars
37k
Forks
3.4k
Avg merge
9h 16m
Merged PRs (30d)
105

Description

1Panel Version

社区版 v2.2.2

Please describe your needs or suggestions for improvements

申请证书的时候一直卡在 waiting for record propagation,如下日志:

2026/06/30 07:37:32 开始申请证书,域名 [example.com,*.example.com],方式 [DNS 自动]DNS 账号 [cf] 厂商 [CloudFlare]
time=2026-06-30T07:37:32.969Z level=INFO msg="Obtaining bundled SAN certificate." domains="example.com, *.example.com"
time=2026-06-30T07:37:34.002Z level=INFO msg="Use solver." domain=*.example.com type=dns-01
time=2026-06-30T07:37:34.002Z level=INFO msg="Use solver." domain=example.com type=dns-01
time=2026-06-30T07:37:34.002Z level=INFO msg="dns01: preparing to solve the challenge." domain=*.example.com
time=2026-06-30T07:37:35.452Z level=INFO msg="dns01: preparing to solve the challenge." domain=example.com
time=2026-06-30T07:37:35.714Z level=INFO msg="dns01: trying to solve the challenge." domain=*.example.com
time=2026-06-30T07:37:35.718Z level=INFO msg="dns01: waiting for record propagation" timeout=30m0s interval=10s domain=*.example.com
time=2026-06-30T08:07:45.794Z level=INFO msg="dns01: waiting for record propagation." domain=*.example.com
time=2026-06-30T08:07:55.799Z level=INFO msg="dns01: trying to solve the challenge." domain=example.com
time=2026-06-30T08:07:55.811Z level=INFO msg="dns01: waiting for record propagation" timeout=30m0s interval=10s domain=example.com

可以看到是 15:37:32 (CST) 开始申请的,但截止到编辑本 issue 的时间 16:21:52 (CST) 为止,日志一直停在这个位置,且状态一直是 申请中。如果我没猜错的话,必须要等到 16:37:55 (CST) 才能结束,我才能再次尝试?

这期间没有任何停止按钮,一个域名就要等他自己超时半小时,两个就要等一个小时,难道只能干等着吗?为什么不能主动停止?

Please describe the solution you suggest

添加一个停止的按钮,允许用户在证书申请时主动停止申请任务

Additional Information

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.