[GH-ISSUE #2082] 0.34.2中 token识别出错 #1655

New issue

Closed

opened 2026-05-05 13:03:28 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 13:03:28 -06:00

Owner

Originally created by @anlen123 on GitHub (Nov 19, 2020).
Original GitHub issue: https://github.com/fatedier/frp/issues/2082

服务端:
[commond]
vhost_http_port = 9091
vhost_https_port = 9092
bind_port = 7000
bind_addr = 0.0.0.0
token = abc

[#frp信息面板端口]
dashboard_port = 7500
dashboard_user = root
dashboard_pwd = ****
subdomain_host = 127.0.0.1

客户端:
[common]
server_addr = ******
server_port = 7000
token = abc

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

报错信息:
2020/11/19 09:10:39 [E] [service.go:279] token in login doesn't match token from configuration
2020/11/19 09:10:39 [W] [service.go:102] login to server failed: token in login doesn't match token from configuration
token in login doesn't match token from configuration

Originally created by @anlen123 on GitHub (Nov 19, 2020). Original GitHub issue: https://github.com/fatedier/frp/issues/2082 服务端: [commond] vhost_http_port = 9091 vhost_https_port = 9092 bind_port = 7000 bind_addr = 0.0.0.0 token = abc [#frp信息面板端口] dashboard_port = 7500 dashboard_user = root dashboard_pwd = **** subdomain_host = 127.0.0.1 客户端: [common] server_addr = ****** server_port = 7000 token = abc [ssh] type = tcp local_ip = 127.0.0.1 local_port = 22 remote_port = 6000 报错信息: 2020/11/19 09:10:39 [E] [service.go:279] token in login doesn't match token from configuration 2020/11/19 09:10:39 [W] [service.go:102] login to server failed: token in login doesn't match token from configuration token in login doesn't match token from configuration

gitea-mirror

2026-05-05 13:03:28 -06:00

closed this issue
added the
lifecycle/stale

need-issue-template
labels

gitea-mirror commented

2026-05-05 13:03:31 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 4, 2021):

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

@github-actions[bot] commented on GitHub (Jan 4, 2021): Issues go stale after 45d of inactivity. Stale issues rot after an additional 10d of inactivity and eventually close.