certimate-go / certimate-go/certimate
[BUG] 使用ca+邮箱 标识acme account 导致 EAB变更不生效
- Dominant language
- Go
- Stars
- 9.3k
- Forks
- 898
- Avg merge
- 4d 5h
- Merged PRs (30d)
- 8
Description
### Description / 功能描述
支持在流程节点中设置使用的 HTTP / HTTPS 代理服务器
### Motivation / 请求动机
因国内某 SSL 证书申请平台疑似针对 IP 做限制:
failed to obtain certificate: acme: error: 401 :: POST :: https://acme.litessl.com/acme/v2/new-order :: urn:ietf:params:acme:error:unauthorized :: The client lacks sufficient authorization
(平台无任何文档提及此错误,网上也没任何相关信息,客服人员无回复)
但是出于安全考虑,所有证书部署的端点(例如 Openresty 等等)都做了 IP 限制,限制死我运行 Certimate 的服务器才能触发 API 更新证书,所以现在的情况是:
我既无法更换服务器 IP,又被迫需要更换服务器 IP.....
所以建议引入流程中独立的 HTTP 代理设计,支持在申请证书环节,或者部署证书环节通过代理服务器来请求(反之成立,比如用一个固定服务器作为代理来申请服务,达到符合部署端点 IP 限制的目的)
### Miscellaneous / 其他
_No response_
### Contribution / 贡献代码
- [ ] I am interested in contributing a PR for this! / 我乐意为此提交代码并发起 PR!
Contributor guide
Research direction
No files, tests, or entry points are named. First reconcile the title's EAB/account claim with the body, then trace the certificate issuance and deployment workflow; done should include independently configurable HTTP/HTTPS proxy support for the relevant requests and coverage for the affected flows.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100