[GH-ISSUE #5157] [Feature Request] IRAN DPI ISSUE #4031

Closed
opened 2026-05-05 14:33:31 -06:00 by gitea-mirror · 3 comments
Owner

Originally created by @dimebage on GitHub (Feb 4, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5157

Describe the feature request

THis was working fine for a long time in iran. tunneling between server in iran and outside iran but very recently as soon as clients connect the connection drop after about 30 seconds.whther tcp or udp both are the same

2026-02-05 01:46:11.103 [I] [server/service.go:576] [60724b3354758ad4] client login info: ip [65.108.61.213:57193] version [0.59.0] hostname [] os [linux] arch [amd64]
2026-02-05 01:46:15.413 [I] [proxy/udp.go:103] [60724b3354758ad4] [ssh] udp proxy listen port [6000]
2026-02-05 01:46:15.413 [I] [server/control.go:399] [60724b3354758ad4] new proxy [ssh] type [udp] success
2026-02-05 01:46:25.915 [W] [server/control.go:289] [60724b3354758ad4] timeout trying to get work connection
2026-02-05 01:46:25.915 [W] [proxy/proxy.go:128] [60724b3354758ad4] [ssh] failed to get work connection: timeout trying to get work connection
2026-02-05 01:46:36.916 [W] [server/control.go:289] [60724b3354758ad4] timeout trying to get work connection
2026-02-05 01:46:36.916 [W] [proxy/proxy.go:128] [60724b3354758ad4] [ssh] failed to get work connection: timeout trying to get work connection
2026-02-05 01:46:47.918 [W] [server/control.go:289] [60724b3354758ad4] timeout trying to get work connection
2026-02-05 01:46:47.918 [W] [proxy/proxy.go:128] [60724b3354758ad4] [ssh] failed to get work connection: timeout trying to get work connection
2026-02-05 01:46:50.983 [I] [proxy/proxy.go:115] [60724b3354758ad4] [ssh] proxy closing

Has the traffic pattern been flagged or it can be something else ?

Describe alternatives you've considered

No response

Affected area

  • Docs
  • Installation
  • Performance and Scalability
  • Security
  • User Experience
  • Test and Release
  • Developer Infrastructure
  • Client Plugin
  • Server Plugin
  • Extensions
  • Others
Originally created by @dimebage on GitHub (Feb 4, 2026). Original GitHub issue: https://github.com/fatedier/frp/issues/5157 ### Describe the feature request THis was working fine for a long time in iran. tunneling between server in iran and outside iran but very recently as soon as clients connect the connection drop after about 30 seconds.whther tcp or udp both are the same 2026-02-05 01:46:11.103 [I] [server/service.go:576] [60724b3354758ad4] client login info: ip [65.108.61.213:57193] version [0.59.0] hostname [] os [linux] arch [amd64] 2026-02-05 01:46:15.413 [I] [proxy/udp.go:103] [60724b3354758ad4] [ssh] udp proxy listen port [6000] 2026-02-05 01:46:15.413 [I] [server/control.go:399] [60724b3354758ad4] new proxy [ssh] type [udp] success 2026-02-05 01:46:25.915 [W] [server/control.go:289] [60724b3354758ad4] timeout trying to get work connection 2026-02-05 01:46:25.915 [W] [proxy/proxy.go:128] [60724b3354758ad4] [ssh] failed to get work connection: timeout trying to get work connection 2026-02-05 01:46:36.916 [W] [server/control.go:289] [60724b3354758ad4] timeout trying to get work connection 2026-02-05 01:46:36.916 [W] [proxy/proxy.go:128] [60724b3354758ad4] [ssh] failed to get work connection: timeout trying to get work connection 2026-02-05 01:46:47.918 [W] [server/control.go:289] [60724b3354758ad4] timeout trying to get work connection 2026-02-05 01:46:47.918 [W] [proxy/proxy.go:128] [60724b3354758ad4] [ssh] failed to get work connection: timeout trying to get work connection 2026-02-05 01:46:50.983 [I] [proxy/proxy.go:115] [60724b3354758ad4] [ssh] proxy closing Has the traffic pattern been flagged or it can be something else ? ### Describe alternatives you've considered _No response_ ### 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:33:31 -06:00
Author
Owner

@fatedier commented on GitHub (Feb 5, 2026):

If this is caused by network/DPI interference, could you try switching the transport protocol and test? For example, set transport.protocol = "kcp" or "quic" on frpc, and enable the corresponding kcpBindPort / quicBindPort on frps. Let us know if KCP/QUIC changes the behavior.

<!-- gh-comment-id:3850743642 --> @fatedier commented on GitHub (Feb 5, 2026): If this is caused by network/DPI interference, could you try switching the transport protocol and test? For example, set transport.protocol = "kcp" or "quic" on frpc, and enable the corresponding kcpBindPort / quicBindPort on frps. Let us know if KCP/QUIC changes the behavior.
Author
Owner

@dimebage commented on GitHub (Feb 5, 2026):

@fatedier
same issue in kcp mode . and in quic mode no connection is made at all to server

Server :
[root@ramin frp_0.59.0_linux_amd64]# ./frps -c frps.toml --log-level debug
2026-02-05 11:28:43.322 [I] [frps/root.go:105] frps uses config file: frps.toml
2026-02-05 11:28:43.756 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:2053
2026-02-05 11:28:43.758 [I] [server/service.go:246] frps kcp listen on udp 0.0.0.0:2053
2026-02-05 11:28:43.758 [I] [frps/root.go:114] frps started successfully
2026-02-05 11:28:43.758 [I] [server/service.go:351] dashboard listen on 0.0.0.0:7500
2026-02-05 11:30:07.409 [I] [server/service.go:576] [0f292c18c23c7167] client login info: ip [65.108.61.213:38041] version [0.59.0] hostname [] os [linux] arch [amd64]
2026-02-05 11:30:16.525 [I] [proxy/udp.go:103] [0f292c18c23c7167] [ssh] udp proxy listen port [6000]
2026-02-05 11:30:16.525 [I] [server/control.go:399] [0f292c18c23c7167] new proxy [ssh] type [udp] success
2026-02-05 11:30:47.289 [I] [proxy/proxy.go:115] [0f292c18c23c7167] [ssh] proxy closing
2026-02-05 11:30:47.289 [W] [proxy/udp.go:121] [0f292c18c23c7167] [ssh] read from workConn for udp error: EOF
2026-02-05 11:30:47.289 [I] [server/control.go:357] [0f292c18c23c7167] client exit success
2026-02-05 11:30:47.289 [I] [proxy/udp.go:162] [0f292c18c23c7167] [ssh] sender goroutine for udp work connection closed
server config :
bindPort =2053
kcpBindPort = 2053
#quicBindPort = 7000
auth.method = "token"
auth.token = "12345678"
webServer.addr = "0.0.0.0"
webServer.port = 7500

dashboard's username and password are both optional

webServer.user = "admin"
webServer.password = "admin"
#tls_enable = true
#transport.tls.enable = true
#transport.tls.force = true
#transport.tls.certFile = "/etc/letsencrypt/live/ramin3.xxx.com/fullchain.pem"
#transport.tls.keyFile = "/etc/letsencrypt/live/ramin3.xxx.com/privkey.pem"

Client :
[root@hetznervps frp_0.59.0_linux_amd64]# ./frpc -c frpc.toml
2026-02-05 07:58:48.770 [I] [sub/root.go:142] start frpc service for config file [frpc.toml]
2026-02-05 07:58:48.771 [I] [client/service.go:294] try to connect to server...
2026-02-05 07:58:49.113 [I] [client/service.go:286] [0f292c18c23c7167] login to server success, get run id [0f292c18c23c7167]
2026-02-05 07:58:49.114 [I] [proxy/proxy_manager.go:173] [0f292c18c23c7167] proxy added: [ssh]
2026-02-05 07:59:27.267 [I] [client/control.go:168] [0f292c18c23c7167] [ssh] start proxy success
2026-02-05 07:59:27.267 [W] [client/control.go:166] [0f292c18c23c7167] [ssh] start error: status not wait start, ignore start message
2026-02-05 07:59:27.771 [I] [proxy/udp.go:93] [0f292c18c23c7167] [ssh] incoming a new work connection for udp proxy, 45.138.132.220:2053
2026-02-05 08:00:07.253 [I] [client/service.go:294] [0f292c18c23c7167] try to connect to server...
2026-02-05 08:00:07.253 [W] [proxy/udp.go:128] [0f292c18c23c7167] [ssh] read from workConn for udp error: EOF
2026-02-05 08:00:07.253 [I] [proxy/udp.go:142] [0f292c18c23c7167] [ssh] writer goroutine for udp work connection closed
2026-02-05 08:00:07.539 [I] [client/service.go:286] [0f292c18c23c7167] login to server success, get run id [0f292c18c23c7167]
2026-02-05 08:00:07.539 [I] [proxy/proxy_manager.go:173] [0f292c18c23c7167] proxy added: [ssh]
2026-02-05 08:00:16.666 [I] [client/control.go:168] [0f292c18c23c7167] [ssh] start proxy success
2026-02-05 08:00:17.167 [I] [proxy/udp.go:93] [0f292c18c23c7167] [ssh] incoming a new work connection for udp proxy, 45.138.132.220:2053
2026-02-05 08:00:47.302 [W] [proxy/udp.go:128] [0f292c18c23c7167] [ssh] read from workConn for udp error: EOF
2026-02-05 08:00:47.302 [I] [proxy/udp.go:142] [0f292c18c23c7167] [ssh] writer goroutine for udp work connection closed
2026-02-05 08:00:47.302 [I] [client/service.go:294] [0f292c18c23c7167] try to connect to server...
2026-02-05 08:00:47.609 [I] [client/service.go:286] [0f292c18c23c7167] login to server success, get run id [0f292c18c23c7167]
2026-02-05 08:00:47.609 [I] [proxy/proxy_manager.go:173] [0f292c18c23c7167] proxy added: [ssh]
^C2026-02-05 08:00:52.298 [I] [sub/root.go:160] frpc service for config file [frpc.toml] stopped

client config :
serverAddr = "ramin3.xxx.com"
serverPort = 2053

auth.method = "token"
auth.token = "12345678"

transport.tls.enable = true
transport.protocol = "kcp"
#transport.protocol = "quic"

proxies
type = "udp"
localIP = "127.0.0.1"
localPort = 1194 # The port on the server where SSH is running
remotePort = 6000 # The port through which you'll access the SSH service via frp
name = "ssh"

In QUIC mode the client can not connect to server at all and nothing reaches the frps . i can see activity in tcpdump but no connection attempt in frps.

<!-- gh-comment-id:3851700165 --> @dimebage commented on GitHub (Feb 5, 2026): @fatedier same issue in kcp mode . and in quic mode no connection is made at all to server Server : [root@ramin frp_0.59.0_linux_amd64]# ./frps -c frps.toml --log-level debug 2026-02-05 11:28:43.322 [I] [frps/root.go:105] frps uses config file: frps.toml 2026-02-05 11:28:43.756 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:2053 2026-02-05 11:28:43.758 [I] [server/service.go:246] frps kcp listen on udp 0.0.0.0:2053 2026-02-05 11:28:43.758 [I] [frps/root.go:114] frps started successfully 2026-02-05 11:28:43.758 [I] [server/service.go:351] dashboard listen on 0.0.0.0:7500 2026-02-05 11:30:07.409 [I] [server/service.go:576] [0f292c18c23c7167] client login info: ip [65.108.61.213:38041] version [0.59.0] hostname [] os [linux] arch [amd64] 2026-02-05 11:30:16.525 [I] [proxy/udp.go:103] [0f292c18c23c7167] [ssh] udp proxy listen port [6000] 2026-02-05 11:30:16.525 [I] [server/control.go:399] [0f292c18c23c7167] new proxy [ssh] type [udp] success 2026-02-05 11:30:47.289 [I] [proxy/proxy.go:115] [0f292c18c23c7167] [ssh] proxy closing 2026-02-05 11:30:47.289 [W] [proxy/udp.go:121] [0f292c18c23c7167] [ssh] read from workConn for udp error: EOF 2026-02-05 11:30:47.289 [I] [server/control.go:357] [0f292c18c23c7167] client exit success 2026-02-05 11:30:47.289 [I] [proxy/udp.go:162] [0f292c18c23c7167] [ssh] sender goroutine for udp work connection closed server config : bindPort =2053 kcpBindPort = 2053 #quicBindPort = 7000 auth.method = "token" auth.token = "12345678" webServer.addr = "0.0.0.0" webServer.port = 7500 # dashboard's username and password are both optional webServer.user = "admin" webServer.password = "admin" #tls_enable = true #transport.tls.enable = true #transport.tls.force = true #transport.tls.certFile = "/etc/letsencrypt/live/ramin3.xxx.com/fullchain.pem" #transport.tls.keyFile = "/etc/letsencrypt/live/ramin3.xxx.com/privkey.pem" Client : [root@hetznervps frp_0.59.0_linux_amd64]# ./frpc -c frpc.toml 2026-02-05 07:58:48.770 [I] [sub/root.go:142] start frpc service for config file [frpc.toml] 2026-02-05 07:58:48.771 [I] [client/service.go:294] try to connect to server... 2026-02-05 07:58:49.113 [I] [client/service.go:286] [0f292c18c23c7167] login to server success, get run id [0f292c18c23c7167] 2026-02-05 07:58:49.114 [I] [proxy/proxy_manager.go:173] [0f292c18c23c7167] proxy added: [ssh] 2026-02-05 07:59:27.267 [I] [client/control.go:168] [0f292c18c23c7167] [ssh] start proxy success 2026-02-05 07:59:27.267 [W] [client/control.go:166] [0f292c18c23c7167] [ssh] start error: status not wait start, ignore start message 2026-02-05 07:59:27.771 [I] [proxy/udp.go:93] [0f292c18c23c7167] [ssh] incoming a new work connection for udp proxy, 45.138.132.220:2053 2026-02-05 08:00:07.253 [I] [client/service.go:294] [0f292c18c23c7167] try to connect to server... 2026-02-05 08:00:07.253 [W] [proxy/udp.go:128] [0f292c18c23c7167] [ssh] read from workConn for udp error: EOF 2026-02-05 08:00:07.253 [I] [proxy/udp.go:142] [0f292c18c23c7167] [ssh] writer goroutine for udp work connection closed 2026-02-05 08:00:07.539 [I] [client/service.go:286] [0f292c18c23c7167] login to server success, get run id [0f292c18c23c7167] 2026-02-05 08:00:07.539 [I] [proxy/proxy_manager.go:173] [0f292c18c23c7167] proxy added: [ssh] 2026-02-05 08:00:16.666 [I] [client/control.go:168] [0f292c18c23c7167] [ssh] start proxy success 2026-02-05 08:00:17.167 [I] [proxy/udp.go:93] [0f292c18c23c7167] [ssh] incoming a new work connection for udp proxy, 45.138.132.220:2053 2026-02-05 08:00:47.302 [W] [proxy/udp.go:128] [0f292c18c23c7167] [ssh] read from workConn for udp error: EOF 2026-02-05 08:00:47.302 [I] [proxy/udp.go:142] [0f292c18c23c7167] [ssh] writer goroutine for udp work connection closed 2026-02-05 08:00:47.302 [I] [client/service.go:294] [0f292c18c23c7167] try to connect to server... 2026-02-05 08:00:47.609 [I] [client/service.go:286] [0f292c18c23c7167] login to server success, get run id [0f292c18c23c7167] 2026-02-05 08:00:47.609 [I] [proxy/proxy_manager.go:173] [0f292c18c23c7167] proxy added: [ssh] ^C2026-02-05 08:00:52.298 [I] [sub/root.go:160] frpc service for config file [frpc.toml] stopped client config : serverAddr = "ramin3.xxx.com" serverPort = 2053 auth.method = "token" auth.token = "12345678" transport.tls.enable = true transport.protocol = "kcp" #transport.protocol = "quic" [[proxies]] type = "udp" localIP = "127.0.0.1" localPort = 1194 # The port on the server where SSH is running remotePort = 6000 # The port through which you'll access the SSH service via frp name = "ssh" In QUIC mode the client can not connect to server at all and nothing reaches the frps . i can see activity in tcpdump but no connection attempt in frps.
Author
Owner

@github-actions[bot] commented on GitHub (Feb 20, 2026):

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

<!-- gh-comment-id:3930962371 --> @github-actions[bot] commented on GitHub (Feb 20, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/frp#4031
No description provided.