We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
frpc 启动时报错 failed to parse proxy proxies.plugin, err: invalid type [https2http]
0.60.0
linux/amd64 Centos7
Enable HTTPS for a local HTTP(S) service
#frps.ini
[common] bind_port = 29000 vhost_http_port = 29003 vhost_https_port = 29007 dashboard_port = 29004 token = ***** max_pool_count = 20 #dashboard 用户名密码,默认都为 admin dashboard_user = ***** dashboard_pwd = ***** log_level = info log_file=/www/frp6.0/frp.log
#frpc.ini
[common] server_addr = ***** server_port = 29000 token = ***** [[proxies]] name = "plugin_https2http" type = "https" customDomains = ["a.example.com"] [proxies.plugin] type = "https2http" localAddr = "192.168.103.104:3377" crtPath = "./fullchain.crt" keyPath = "./private.pem" hostHeaderRewrite = "127.0.0.1" requestHeaders.set.x-from-where = "frp" #log.to = "./frpc.log"
无
[root@logfile frp6.0]# ./frpc -c frpc.ini failed to parse proxy proxies.plugin, err: invalid type [https2http]
The text was updated successfully, but these errors were encountered:
新(toml)旧(ini)格式不可混用,选择一种 (建议)https://github.com/fatedier/frp/tree/dev/conf https://github.com/fatedier/frp/tree/dev/conf/legacy
Sorry, something went wrong.
Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.
No branches or pull requests
Bug Description
frpc 启动时报错 failed to parse proxy proxies.plugin, err: invalid type [https2http]
frpc Version
0.60.0
frps Version
0.60.0
System Architecture
linux/amd64 Centos7
Configurations
Enable HTTPS for a local HTTP(S) service
#frps.ini
#frpc.ini
Logs
无
Steps to reproduce
Affected area
The text was updated successfully, but these errors were encountered: