mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #5255] 貌似远程地址不能填写服务器域名,这不方便,能否修改下(0.53版本) #4069
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#4069
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 @huangyixin447 on GitHub (Mar 20, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5255
Bug Description
貌似远程地址不能填写服务器域名,这不方便,能否修改下(0.53版本)
会报错远程服务器拒绝链接
frpc Version
0.53
frps Version
0.53
System Architecture
win、mac、linux(ubuntu)
Configurations
serverAddr = "xxxxxx"
serverPort = 7000
Logs
frpc.exe -c frpc.toml
2026/03/20 17:56:19 [I] [root.go:139] start frpc service for config file [frpc.toml]
2026/03/20 17:56:19 [W] [service.go:131] login to server failed: read tcp 192.168.0.103:8295->xxxxxx:7000: wsarecv: An existing connection was forcibly closed by the remote host.
2026/03/20 17:56:19 [I] [root.go:154] frpc service for config file [frpc.toml] stopped
Steps to reproduce
...
Affected area
@Rekoe commented on GitHub (Mar 22, 2026):
自己写一个初始化脚本 通过ping的方式获取域名Ip
@ly360 commented on GitHub (Mar 25, 2026):
serverAddr可以填写域名,检查下是不是用了大陆境内节点使用了未备案域名
@zhenxin0603 commented on GitHub (Apr 1, 2026):
我这0.68 域名工作正常,0.53没试。
@zzjjbb commented on GitHub (Apr 9, 2026):
默认使用TLS,使用带着域名访问的话,frps的证书和域名不匹配就会出问题。我发现可以
transport.tls.enable = false
临时解决这个问题
@ZER-ONE commented on GitHub (Apr 10, 2026):
请问要如何设置域名访问呢?可以发一下你的frpc.toml配置单吗?
非常感谢
@zzjjbb commented on GitHub (Apr 11, 2026):
这种不用设置,默认填IP的地方几乎都是可以填的吧,除了和tls/web相关的一些问题
@github-actions[bot] commented on GitHub (Apr 26, 2026):
Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.