github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #4125] suddenly connect to server error: connection write timeout #3254

New issue

Closed

opened 2026-05-05 14:06:03 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 14:06:03 -06:00

Owner

Originally created by @solo7773 on GitHub (Apr 3, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4125

Bug Description

I used version 0.51.0 and it worked as expected. But since Jan 2024, frpc cannot connect to frps.

I then tried the newest 0.56.0, the error is the same as that of 0.51.0

frpc Version

0.56.0

frps Version

0.56.0

System Architecture

linux/amd64, darwin/amd64

Configurations

Server, ubuntu 22.04

# frps.toml
bindPort = 7000

Client, macOS and cent os

# frpc.toml
serverAddr = "x.x.x.x"
serverPort = 7000

proxies
name = "ssh"
type = "tcp"
localIP = "127.0.0.1"
localPort = 22
remotePort = 6000

Logs

frps and frpc were run by non-root user

./frps -c ./frps.toml

./frpc -c ./frpc.toml

frps logging

2024-04-03 11:50:08.582 [I] [frps/root.go:105] frps uses config file: frps.toml

2024-04-03 11:50:09.044 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:7000

2024-04-03 11:50:09.044 [I] [frps/root.go:114] frps started successfully

frpc logging

2024-04-03 11:56:46.489 [I] [sub/root.go:142] start frpc service for config file [frpc.toml]

2024-04-03 11:56:46.490 [I] [client/service.go:294] try to connect to server...

2024-04-03 11:56:56.604 [W] [client/service.go:297] connect to server error: connection write timeout

2024-04-03 11:56:56.605 [I] [sub/root.go:160] frpc service for config file [frpc.toml] stopped

login to the server failed: connection write timeout. With loginFailExit enabled, no additional retries will be attempted

follow up

I then checked server logging, but there is no in-connection from the client.

client to server connection is ok

nc -z x.x.x.x 7000

Connection to x.x.x.x port 7000 [tcp/*] succeeded!

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 @solo7773 on GitHub (Apr 3, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4125 ### Bug Description I used version 0.51.0 and it worked as expected. But since Jan 2024, frpc cannot connect to frps. I then tried the newest 0.56.0, the error is the same as that of 0.51.0 ### frpc Version 0.56.0 ### frps Version 0.56.0 ### System Architecture linux/amd64, darwin/amd64 ### Configurations # Server, ubuntu 22.04 \# frps.toml bindPort = 7000 # Client, macOS and cent os \# frpc.toml serverAddr = "x.x.x.x" serverPort = 7000 [[proxies]] name = "ssh" type = "tcp" localIP = "127.0.0.1" localPort = 22 remotePort = 6000 ### Logs frps and frpc were run by non-root user `./frps -c ./frps.toml` `./frpc -c ./frpc.toml` # frps logging 2024-04-03 11:50:08.582 [I] [frps/root.go:105] frps uses config file: frps.toml 2024-04-03 11:50:09.044 [I] [server/service.go:237] frps tcp listen on 0.0.0.0:7000 2024-04-03 11:50:09.044 [I] [frps/root.go:114] frps started successfully # frpc logging 2024-04-03 11:56:46.489 [I] [sub/root.go:142] start frpc service for config file [frpc.toml] 2024-04-03 11:56:46.490 [I] [client/service.go:294] try to connect to server... 2024-04-03 11:56:56.604 [W] [client/service.go:297] connect to server error: connection write timeout 2024-04-03 11:56:56.605 [I] [sub/root.go:160] frpc service for config file [frpc.toml] stopped login to the server failed: connection write timeout. With loginFailExit enabled, no additional retries will be attempted # follow up I then checked server logging, but there is no in-connection from the client. # client to server connection is ok nc -z x.x.x.x 7000 Connection to x.x.x.x port 7000 [tcp/*] succeeded! ### Steps to reproduce no ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [X] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:06:03 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

@xqzr commented on GitHub (Apr 3, 2024):

openssl s_client -connect x.x.x.x:7000

@xqzr commented on GitHub (Apr 3, 2024): ```shell openssl s_client -connect x.x.x.x:7000 ```

gitea-mirror commented

2026-05-05 14:06:07 -06:00

Author

Owner

@solo7773 commented on GitHub (Apr 4, 2024):

openssl s_client -connect x.x.x.x:7000

Hi @xqzr ,

Thanks! I run your command and get the output. Please see below and help me to solve the problem.

CONNECTED(00000003)
depth=0 
verify error:num=18:self signed certificate
verify return:1
depth=0 
verify error:num=13:format error in certificate's notBefore field
notBefore=Jan  1 00:00:00 1 GMT
verify return:1
depth=0 
verify error:num=14:format error in certificate's notAfter field
notAfter=Jan  1 00:00:00 1 GMT
verify return:1
depth=0 
notAfter=Jan  1 00:00:00 1 GMT
verify return:1
---
Certificate chain
 0 s:
   i:
---
Server certificate
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
subject=
issuer=
---
No client certificate CA names sent
Server Temp Key: ECDH, X25519, 253 bits
---
SSL handshake has read 1221 bytes and written 289 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    ....
    Start Time: 1712218494
    Timeout   : 7200 (sec)
    Verify return code: 14 (format error in certificate's notAfter field)
---

@solo7773 commented on GitHub (Apr 4, 2024): > ```shell > openssl s_client -connect x.x.x.x:7000 > ``` Hi @xqzr , Thanks! I run your command and get the output. Please see below and help me to solve the problem. ``` CONNECTED(00000003) depth=0 verify error:num=18:self signed certificate verify return:1 depth=0 verify error:num=13:format error in certificate's notBefore field notBefore=Jan 1 00:00:00 1 GMT verify return:1 depth=0 verify error:num=14:format error in certificate's notAfter field notAfter=Jan 1 00:00:00 1 GMT verify return:1 depth=0 notAfter=Jan 1 00:00:00 1 GMT verify return:1 --- Certificate chain 0 s: i: --- Server certificate -----BEGIN CERTIFICATE----- -----END CERTIFICATE----- subject= issuer= --- No client certificate CA names sent Server Temp Key: ECDH, X25519, 253 bits --- SSL handshake has read 1221 bytes and written 289 bytes --- New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256 Server public key is 2048 bit Secure Renegotiation IS supported Compression: NONE Expansion: NONE No ALPN negotiated SSL-Session: Protocol : TLSv1.2 .... Start Time: 1712218494 Timeout : 7200 (sec) Verify return code: 14 (format error in certificate's notAfter field) --- ```

gitea-mirror commented

2026-05-05 14:06:07 -06:00

Author

Owner

@solo7773 commented on GitHub (Apr 4, 2024):

Add the following setting to frpc solve the error

transport.tls.enable = false

@solo7773 commented on GitHub (Apr 4, 2024): Add the following setting to frpc solve the error `transport.tls.enable = false`

gitea-mirror commented

2026-05-05 14:06:07 -06:00

Author

Owner

@xqzr commented on GitHub (Apr 4, 2024):

openssl s_client -connect x.x.x.x:7000

Hi @xqzr ,

Thanks! I run your command and get the output. Please see below and help me to solve the problem.

CONNECTED(00000003)
depth=0 
verify error:num=18:self signed certificate
verify return:1
depth=0 
verify error:num=13:format error in certificate's notBefore field
notBefore=Jan  1 00:00:00 1 GMT
verify return:1
depth=0 
verify error:num=14:format error in certificate's notAfter field
notAfter=Jan  1 00:00:00 1 GMT
verify return:1
depth=0 
notAfter=Jan  1 00:00:00 1 GMT
verify return:1
---
Certificate chain
 0 s:
   i:
---
Server certificate
-----BEGIN CERTIFICATE-----

-----END CERTIFICATE-----
subject=
issuer=
---
No client certificate CA names sent
Server Temp Key: ECDH, X25519, 253 bits
---
SSL handshake has read 1221 bytes and written 289 bytes
---
New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256
Server public key is 2048 bit
Secure Renegotiation IS supported
Compression: NONE
Expansion: NONE
No ALPN negotiated
SSL-Session:
    Protocol  : TLSv1.2
    ....
    Start Time: 1712218494
    Timeout   : 7200 (sec)
    Verify return code: 14 (format error in certificate's notAfter field)
---

连接没有问题。
可能是你所在的网络，对 TLS 存在过滤

@xqzr commented on GitHub (Apr 4, 2024): > > ```shell > > openssl s_client -connect x.x.x.x:7000 > > ``` > > Hi @xqzr , > > Thanks! I run your command and get the output. Please see below and help me to solve the problem. > > ``` > CONNECTED(00000003) > depth=0 > verify error:num=18:self signed certificate > verify return:1 > depth=0 > verify error:num=13:format error in certificate's notBefore field > notBefore=Jan 1 00:00:00 1 GMT > verify return:1 > depth=0 > verify error:num=14:format error in certificate's notAfter field > notAfter=Jan 1 00:00:00 1 GMT > verify return:1 > depth=0 > notAfter=Jan 1 00:00:00 1 GMT > verify return:1 > --- > Certificate chain > 0 s: > i: > --- > Server certificate > -----BEGIN CERTIFICATE----- > > -----END CERTIFICATE----- > subject= > issuer= > --- > No client certificate CA names sent > Server Temp Key: ECDH, X25519, 253 bits > --- > SSL handshake has read 1221 bytes and written 289 bytes > --- > New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES128-GCM-SHA256 > Server public key is 2048 bit > Secure Renegotiation IS supported > Compression: NONE > Expansion: NONE > No ALPN negotiated > SSL-Session: > Protocol : TLSv1.2 > .... > Start Time: 1712218494 > Timeout : 7200 (sec) > Verify return code: 14 (format error in certificate's notAfter field) > --- > ``` 连接没有问题。可能是你所在的网络，对 TLS 存在过滤

gitea-mirror commented

2026-05-05 14:06:08 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 26, 2024):

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

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

gitea-mirror referenced this issue

2026-05-05 14:47:16 -06:00

[PR #3254] [MERGED] optimize: GetAuthKey #4711

gitea-mirror referenced this issue

2026-05-05 14:47:27 -06:00

[PR #3299] [MERGED] sync #4720