mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #2268] STCP模式偶尔会显示监听成功但无法连接的问题 #1801
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#1801
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @worksg on GitHub (Mar 2, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2268
Originally assigned to: @yuyulei on GitHub.
[REQUIRED] hat version of frp are you using
服务器
frps --version
0.33.0
客户端(stcp role: server)
frpc --version
0.34.0
客户端(stcp role: visitor)
frpc --version
0.34.3
[REQUIRED] What operating system and processor architecture are you using
OS:
CPU architecture:
[REQUIRED] description of errors
confile
FRPS SERVER
STCP ROLE: SERVER
STCP ROLE: VISITOR
log file
FRPS SERVER LOG
FRPC STCP SERVER
FRPC STCP VISITOR
Steps to reproduce the issue
不定期出现,不能通过固定的步骤复现问题
Supplementary information
看日志基本就是stcp server监听是正常的,但stcp visitor访问stcp server后就立刻看到服务器的stcp server closing了,然后stcp server立刻重新监听,然后stcp visitor访问stcp server又看到服务器的stcp server closing,然后stcp server又重新监听,周而复始基本就是这样
这个问题经常能遇到,有时一周不到出现,有时一两个月或更久才出现,之前服务端没有开启长时间保存日志,所以出现问题有时拖了一阵子日志被清空了
重启FRPS能暂时解决问题,重启STCP SERVER和STCP VISITOR不能解决问题
Can you guess what caused this issue
Checklist:
@fatedier commented on GitHub (Mar 2, 2021):
看起来更像是网络问题,可能是网络不稳定导致的。
也可以启动 TLS 试试。
@worksg commented on GitHub (Mar 2, 2021):
我改成TLS运行了,看看过阵子会不会触发这个问题吧
@worksg commented on GitHub (Mar 2, 2021):
自签证TLS在FRPC配置里可以支持自定义ServerName吗,只能用server_addr作为ServerName感觉不太灵活,有时候内网环境会做域名过滤,不给解析外网DNS,虽然可以改hosts文件解决但没系统的管理员权限就比较麻烦。
@fatedier commented on GitHub (Mar 3, 2021):
@yuyulei 跟一下这个问题吧,应该是可以支持设置 tls_server_name 参数来覆盖
@yuyulei commented on GitHub (Mar 4, 2021):
@worksg 生成 tls 签名的时候是支持自定义域名和 ip 的,现在是有什么问题呢?
@fatedier commented on GitHub (Mar 4, 2021):
@yuyulei 参考 kubectl 提供的 --tls-server-name 的功能,覆盖请求地址的 Host