[GH-ISSUE #5024] 多层网络嵌套socks代理认证问题

gitea-mirror commented

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

Owner

Copy link

Originally created by @Archerkong on GitHub (Oct 17, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5024

Bug Description

我发现当我使用如下frpc配置文件进行设置时，username = "abc"
password = "abc"部分无法生效，连接时不需要输入密码就可以使用，请问该怎么解决？

frpc Version

0.65.0

frps Version

0.65.0

System Architecture

linux/amd64

Configurations

serverAddr = "vps"
serverPort = 7000
auth.token = "123456"

proxies
name = "socks1"
type = "tcp"
remotePort = 1071
[proxies.plugin]
type = "socks5"
username = "abc"
password = "abc"
proxies
name = "socks2"
type = "tcp"
localIP = "127.0.0.1"
localPort = 1072
remotePort = 1073

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 @Archerkong on GitHub (Oct 17, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5024 ### Bug Description 我发现当我使用如下frpc配置文件进行设置时，username = "abc" password = "abc"部分无法生效，连接时不需要输入密码就可以使用，请问该怎么解决？ ### frpc Version 0.65.0 ### frps Version 0.65.0 ### System Architecture linux/amd64 ### Configurations serverAddr = "vps" serverPort = 7000 auth.token = "123456" [[proxies]] name = "socks1" type = "tcp" remotePort = 1071 [proxies.plugin] type = "socks5" username = "abc" password = "abc" [[proxies]] name = "socks2" type = "tcp" localIP = "127.0.0.1" localPort = 1072 remotePort = 1073 ### 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:05 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

Copy link

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

No Branch/Tag specified