certimate-go / certimate-go/certimate

[Bug] 部署到edgeone makers失败,国际国内版都失败

Open
#1,384 19 comments 0 reactions 0 assignees View on GitHub
bug help wanted
Dominant language
Go
Stars
9.3k
Forks
898
Avg merge
4d 5h
Merged PRs (30d)
8

Description

### Release Version / 软件版本

0.4.28

### Description / 缺陷描述

部署到腾讯云edgeone makers失败

### 一、部署到edgeone国际版
提示“failed to execute sdk request 'teo.makers.DescribePagesZoneCustomDomains': sdkerr: api error: code='109', message='The Token usage region is incorrect.'”
### 二、部署到edgeone国内版
# 1.如果设置“根据证书自动匹配”
提示“[2026-07-22 12:11:17]
api request 'teo.makers.DescribePagesZoneCustomDomains'
[2026-07-22 12:11:17]
could not deploy certificate
[2026-07-22 12:11:17]
could not find any domains matched by certificate”
# 2.如果精准设置一个域名
提示“workflow engine panic: runtime error: index out of range [0] with length 0”
(此处错误不显示在日志框,如图,日志框里面根本不提示任何错误)
Image

### Steps to reproduce / 复现步骤

1.设置流程,部署到腾讯云edgeone国内版和国际版;
2.如果是国际版,填写接口端点,如果是国内版,留空;
3.国际版和国内版的token已经分别申请并填写;
4.运行流程。

### Logs / 日志

已在缺陷描述中上传

### Miscellaneous / 其他

### Contribution / 贡献代码

- [x] I am interested in contributing a PR for this! / 我乐意为此提交代码并发起 PR!

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the EdgeOne domestic and international deployment paths described in the issue, using the supplied API errors and certificate-matching settings. Trace the EdgeOne deployment entry point and workflow-engine error handling; done means both regional paths handle the reported API failures without a panic and surface useful errors in the log.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cloud, devops
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.