---
title: "Solution to 1Panel CloudFlare Certificate Application Failure"
url: https://www.geekcorelab.cn/en-US/post/solution-to-failed-certificate-application-for-1panel
updated: 2026-11-02T14:28:06.855362Z
author: "hhjmk"
summary: "升级1Panel后使用CloudFlare DNS验证时出现错误，需创建新的API Token解决。具体步骤包括在CloudFlare创建API令牌并选择对应域，然后在1Panel的DNS账户中替换API Key为该令牌。申请证书时建议使用RSA2048密钥算法。文章指出1Panel在提示时应使用API Token而非API Key，以避免用户混淆。"
---

# Solution to 1Panel CloudFlare Certificate Application Failure

After upgrading 1Panel, when using CloudFlare DNS verification, the following prompt appears: `[*.biliwind.com] [*.biliwind.com] acme: error presenting token: cloudflare: failed to find zone biliwind.com.: ListZonesContext command failed: Invalid request headers (6003)`

To solve this problem, we need to create a new API Token instead of using the Global API Key

![](/uploads/import-placeholder/331)
First, after logging in at [dash.cloudflare.com](http://dash.cloudflare.com/), click the person icon in the upper right corner, then click My Profile

![](/uploads/import-placeholder/339)
Click API Tokens, then Create Token

![](/uploads/import-placeholder/13)
Click “Use template” next to Edit zone DNS

Select the domain you want to use in the second column

![](/uploads/import-placeholder/5)
Scroll to the bottom and click “Continue to show summary”

After confirming, your token will be displayed; this token is displayed only once

![](/uploads/import-placeholder/301)
Find the DNS account in 1Panel

![](/uploads/import-placeholder/365)
Edit the existing account

![](/uploads/import-placeholder/186)
Replace the API key with the API Token

![](/uploads/import-placeholder/240)
When applying for a certificate, if it is a previously created ACME account, select the RSA2048 key algorithm

![](/uploads/import-placeholder/119)
If it is a newly installed server from [雨云](https://www.rainyun.com/github_) with 1Panel preinstalled

![](/uploads/import-placeholder/280)
When creating an account, it is recommended to set the key algorithm to RSA2048

![](/uploads/import-placeholder/327)
and also select RSA2048 when applying for the certificate

---

Reference articles:

[v1.9 Version CloudFlare Certificate Application Failure Solution - 1Panel - Community Forum - FIT2CLOUD 飞致云](https://bbs.fit2cloud.com/t/topic/2541)  
[Latest v1.9.1 CloudFlare Certificate Application Failure - 1Panel - Community Forum - FIT2CLOUD 飞致云](https://bbs.fit2cloud.com/t/topic/2597)

![](/uploads/import-placeholder/369)
The only downside is that although it has already been changed to API Token, the panel should prompt when applying for a certificate and change the text to API Token instead of API Key

Because CloudFlare originally intended to translate API Token as “API令牌”

![](/uploads/import-placeholder/62)

![](/uploads/import-placeholder/334)
In addition, the name Global API Key fully contains the keyword “API Key”

![](/uploads/import-placeholder/348)
This can easily mislead users
