gitea-mirror commented

Owner

Originally created by @NingLiu1998 on GitHub (Apr 18, 2023).
Original GitHub issue: https://github.com/fatedier/frp/issues/3415

Bug Description

D:\ln2023\OtherProject\frp_0.48.0_windows_amd64>frpc -c frpc.ini
2023/04/18 11:37:11 [W] [service.go:134] login to server failed: i/o deadline reached
i/o deadline reached

D:\ln2023\OtherProject\frp_0.48.0_windows_amd64>frpc -c frpc.ini
2023/04/18 11:45:10 [W] [service.go:134] login to server failed: i/o deadline reached
i/o deadline reached

D:\ln2023\OtherProject\frp_0.48.0_windows_amd64>frpc -c frpc.ini
2023/04/18 11:46:09 [W] [service.go:134] login to server failed: i/o deadline reached
i/o deadline reached

D:\ln2023\OtherProject\frp_0.48.0_windows_amd64>frpc -c frpc.ini
2023/04/18 11:47:17 [W] [service.go:134] login to server failed: i/o deadline reached
i/o deadline reached

从下载下来然后运行，一直报这个错 😳

frpc Version

0.48.0

frps Version

0.48.0

System Architecture

windows/amd64

Configurations

frpc.ini

[common]
server_addr =  xx.xxx.xx.xx
server_port = 7388
token = a123456789

[ssh]
type = tcp
local_ip = 127.0.0.1
local_port = 22
remote_port = 6000


[web]
type = http
local_port = 5000
custom_domains = a2.xxx.com

frps.ini

[common]
bind_port = 7700
vhost_http_port = 7388
authentication_method = token
token = a123456789

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 @NingLiu1998 on GitHub (Apr 18, 2023). Original GitHub issue: https://github.com/fatedier/frp/issues/3415 ### Bug Description ``` D:\ln2023\OtherProject\frp_0.48.0_windows_amd64>frpc -c frpc.ini 2023/04/18 11:37:11 [W] [service.go:134] login to server failed: i/o deadline reached i/o deadline reached D:\ln2023\OtherProject\frp_0.48.0_windows_amd64>frpc -c frpc.ini 2023/04/18 11:45:10 [W] [service.go:134] login to server failed: i/o deadline reached i/o deadline reached D:\ln2023\OtherProject\frp_0.48.0_windows_amd64>frpc -c frpc.ini 2023/04/18 11:46:09 [W] [service.go:134] login to server failed: i/o deadline reached i/o deadline reached D:\ln2023\OtherProject\frp_0.48.0_windows_amd64>frpc -c frpc.ini 2023/04/18 11:47:17 [W] [service.go:134] login to server failed: i/o deadline reached i/o deadline reached ``` 从下载下来然后运行，一直报这个错 😳 ### frpc Version 0.48.0 ### frps Version 0.48.0 ### System Architecture windows/amd64 ### Configurations # frpc.ini ```ini [common] server_addr = xx.xxx.xx.xx server_port = 7388 token = a123456789 [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000 [web] type = http local_port = 5000 custom_domains = a2.xxx.com ``` # frps.ini ```ini [common] bind_port = 7700 vhost_http_port = 7388 authentication_method = token token = a123456789 ``` ### Logs _No response_ ### Steps to reproduce 1. 下载最新版本 🦵🏼 2. 调整配置部署服务端 🥰 3. 启动客户端 🥴 ### 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 13:45:36 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 13:45:41 -06:00

Author

Owner

@Daiyangcheng commented on GitHub (Apr 18, 2023):

frpc.ini 那边的 server_port 应该填写 frps.ini 里面的 bind_port 字段的内容，这并不是Bug，是你自己的问题

@Daiyangcheng commented on GitHub (Apr 18, 2023): frpc.ini 那边的 server_port 应该填写 frps.ini 里面的 bind_port 字段的内容，这并不是Bug，是你自己的问题

gitea-mirror commented

2026-05-05 13:45:41 -06:00

Author

Owner

@NingLiu1998 commented on GitHub (Apr 21, 2023):

感谢，俺搞迷糊了

@NingLiu1998 commented on GitHub (Apr 21, 2023): 感谢，俺搞迷糊了

gitea-mirror commented

2026-05-05 13:45:42 -06:00

Author

Owner

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