mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #4650] Unable to Connect with Token Configured in frps.ini and frpc.ini (version 0.61.1) #3674
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#3674
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 @Surtryyds on GitHub (Jan 26, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4650
Bug Description
I am experiencing an issue with FRP version 0.61.1 (using the frp_0.61.1_linux_arm64.tar.gz package) while running both frps and frpc in Docker on an Ubuntu 24.04 server. Specifically, when I configure the token in both the frps.ini and frpc.ini files, the connection fails. The only way I can get the connection to work is by removing the token configuration entirely.
Steps to Reproduce:
Use the frp_0.61.1_linux_arm64.tar.gz release and extract it on both the server and client.
Configure the token parameter in both the frps.ini and frpc.ini files (make sure they match).
Run both frps and frpc containers using Docker.
The connection will fail when the token is configured.
Expected Behavior:
The token should allow the client (frpc) to connect to the server (frps) without issues.
Actual Behavior:
The connection fails when the token is configured. If I remove the token from both the frps.ini and frpc.ini, the connection is successful.
frpc Version
0.61.1
frps Version
0.61.1
System Architecture
Linux/ARM64
Configurations
frps.ini:
[common]
bind_port = 7000
vhost_http_port = 80
dashboard_addr = 0.0.0.0
dashboard_port = 7500
dashboard_user = admin
dashboard_pwd = admin123
serverAddr = "your_server_ip"
serverPort = 7000
token = "your_token"
frpc.ini:
[common]
server_addr = "your_server_ip"
server_port = 7000
token = "your_token"
[remote-ssh]
type = tcp
local_ip = "127.0.0.1"
local_port = 22
remote_port = 22
Logs
No response
Steps to reproduce
...
Affected area
@xqzr commented on GitHub (Jan 28, 2025):
对于
.ini不需要双引号(")@Surtryyds commented on GitHub (Jan 28, 2025):
我用了.toml 配置还是一样的问题，我尝试改了源码，增加了调试输出，发现程序从配置文件获取的config中的token加密值和匹配值一直对不上，但是我检查我的服务端和客户端的token是一样的，我索性把源代码中的md5的token加密删了,只保留token+时间戳就能连了。
@Surtryyds commented on GitHub (Jan 28, 2025):
因为我是在docker中运行的，我还特意检查了时区是一样的，token也是一样的，但是仍然连不上，我觉得是0.61.1有bug，我朋友用的远古版本的frp就能用token连上。
@Surtryyds commented on GitHub (Jan 28, 2025):
这样配置也是显示token对不上的
@WongIong commented on GitHub (Jan 28, 2025):
frps加上 bindAddr = "XXXX" 試試呢?
@superzjg commented on GitHub (Jan 29, 2025):
先不用docker，用普通环境试一试。
@github-actions[bot] commented on GitHub (Feb 13, 2025):
Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.
@lendy98 commented on GitHub (Feb 14, 2025):
auth.method = "token"
@github-actions[bot] commented on GitHub (Mar 1, 2025):
Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.