[GH-ISSUE #3635] proxy_protocol似乎不能与unix_domain_socket同时使用

gitea-mirror commented

2026-05-05 13:52:25 -06:00

Owner

Copy link

Originally created by @imzlh on GitHub (Sep 29, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3635

Bug Description

nginx显示:2023/09/29 11:52:07 [error] 18572#18572: *15 broken header: "...(乱码)..." while reading PROXY protocol, client: unix:, server: unix:/run/io_http2.sock
猜测是插件与proxy_protocol不能同时使用

frpc Version

0.51.3

frps Version

0.48.0

System Architecture

linux/amd64

Configurations

[https]
type = https
plugin = unix_domain_socket
plugin_unix_path = /run/io_http2.sock
proxy_protocol = v2

Logs

没有错误输出

Steps to reproduce

重启FRPC后直接访问网址

Affected area

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

Originally created by @imzlh on GitHub (Sep 29, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3635 ### Bug Description nginx显示:`2023/09/29 11:52:07 [error] 18572#18572: *15 broken header: "...(乱码)..." while reading PROXY protocol, client: unix:, server: unix:/run/io_http2.sock` 猜测是插件与proxy_protocol不能同时使用 ### frpc Version 0.51.3 ### frps Version 0.48.0 ### System Architecture linux/amd64 ### Configurations [https] type = https plugin = unix_domain_socket plugin_unix_path = /run/io_http2.sock proxy_protocol = v2 ### Logs 没有错误输出 ### Steps to reproduce 重启FRPC后直接访问网址 ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [X] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 13:52:25 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:52:29 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Oct 30, 2023):

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

@github-actions[bot] commented on GitHub (Oct 30, 2023): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

No Branch/Tag specified