[GH-ISSUE #5036] 配置证书时报错

gitea-mirror commented

2026-05-05 14:31:15 -06:00

Owner

Copy link

Originally created by @holalahy on GitHub (Oct 30, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5036

Bug Description

根据文档示例，在win10客户端中采用https方式配置证书
crtPath = "./ca/xxx.pem" keyPath = "./ca/xxx.key"
启动客户端时报错：
D:\server\frp>frpc -c frpc.toml
unmarshal ProxyConfig error: json: unknown field "crtPath"

frpc Version

0.65.0

frps Version

0.65.04l

System Architecture

windows/amd64

Configurations

serverAddr = "x.x.x.x"
serverPort = 7000

proxies
name = "web"
type = "https"
localPort = 9999
customDomains = ["xx.xxx.com"]
crtPath = "./ca/xxx.pem"
keyPath = "./ca/xxx.key"

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @holalahy on GitHub (Oct 30, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5036 ### Bug Description 根据文档示例，在win10客户端中采用https方式配置证书 `crtPath = "./ca/xxx.pem" keyPath = "./ca/xxx.key"` 启动客户端时报错： D:\server\frp>frpc -c frpc.toml unmarshal ProxyConfig error: json: unknown field "crtPath" ### frpc Version 0.65.0 ### frps Version 0.65.04l ### System Architecture windows/amd64 ### Configurations serverAddr = "x.x.x.x" serverPort = 7000 [[proxies]] name = "web" type = "https" localPort = 9999 customDomains = ["xx.xxx.com"] crtPath = "./ca/xxx.pem" keyPath = "./ca/xxx.key" ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:31:15 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:31:18 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Nov 14, 2025):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Nov 14, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:50:20 -06:00

[PR #3963] [MERGED] web: support to clear offline proxies data on dashboard #4873

No Branch/Tag specified