[GH-ISSUE #4031] register control error: token in login doesn't match token from configuration in v0.54.0

gitea-mirror commented

2026-05-05 14:03:50 -06:00

Owner

Originally created by @tcexeexe on GitHub (Feb 28, 2024).
Original GitHub issue: https://github.com/fatedier/frp/issues/4031

Bug Description

error in sevice
2024/02/28 10:09:07 [W] [service.go:433] register control error: token in login doesn't match token from configuration
error in client

2024/02/28 10:09:07 [I] [root.go:160] frpc service for config file [frpc.toml] stopped
login to the server failed: token in login doesn't match token from configuration. With loginFailExit enabled, no additional retries will be attempted

Do you know what's wrong with it?

frpc Version

0.54.0

frps Version

0.54.0

System Architecture

linux/amd64

Configurations

frpc:

serverAddr = "xx.xx.xx.xx"
serverPort = xxxx
auth.token = "abc"

[[proxies]]
name = "ssh"
type = "tcp"
localIP = "127.0.0.1"
localPort = 22
remotePort = 6000

frps:

[common]
bind_port = 20000
auth.method = "token"
auth.token = "abc"

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 @tcexeexe on GitHub (Feb 28, 2024). Original GitHub issue: https://github.com/fatedier/frp/issues/4031 ### Bug Description error in sevice `2024/02/28 10:09:07 [W] [service.go:433] register control error: token in login doesn't match token from configuration` error in client ``` 2024/02/28 10:09:07 [I] [root.go:160] frpc service for config file [frpc.toml] stopped login to the server failed: token in login doesn't match token from configuration. With loginFailExit enabled, no additional retries will be attempted ``` Do you know what's wrong with it? ### frpc Version 0.54.0 ### frps Version 0.54.0 ### System Architecture linux/amd64 ### Configurations frpc: ``` serverAddr = "xx.xx.xx.xx" serverPort = xxxx auth.token = "abc" [[proxies]] name = "ssh" type = "tcp" localIP = "127.0.0.1" localPort = 22 remotePort = 6000 ``` frps: ``` [common] bind_port = 20000 auth.method = "token" auth.token = "abc" ``` ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [ ] Installation - [ ] Performance and Scalability - [x] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:03:50 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:03:54 -06:00

Author

Owner

@superzjg commented on GitHub (Feb 29, 2024):

~~[common]~~
bindPort = 20000

@superzjg commented on GitHub (Feb 29, 2024): ~~[common]~~ `bindPort = 20000`

gitea-mirror commented

2026-05-05 14:03:55 -06:00

Author

Owner

@MiuKaShi commented on GitHub (Mar 5, 2024):

I found that even it connected successfully (version 0.54.0), I still get
[service.go:433] register control error: token in login doesn't match token from configuration
bug ?

@MiuKaShi commented on GitHub (Mar 5, 2024): I found that even it connected successfully (version 0.54.0), I still get `[service.go:433] register control error: token in login doesn't match token from configuration` bug ?

gitea-mirror commented

2026-05-05 14:03:55 -06:00

Author

Owner

@linyuxuanlin commented on GitHub (Mar 10, 2024):

I met the same issue in 0.54.0, with no token I can connect normally. But with the same token configured both on frps and frpc, I can't connect. The error message was:

login to the server failed: token in login doesn't match token from configuration. With loginFailExit enabled, no additional retries will be attempted

@linyuxuanlin commented on GitHub (Mar 10, 2024): I met the same issue in 0.54.0, with no token I can connect normally. But with the same token configured both on frps and frpc, I can't connect. The error message was: ``` login to the server failed: token in login doesn't match token from configuration. With loginFailExit enabled, no additional retries will be attempted ```

gitea-mirror commented

2026-05-05 14:03:56 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 1, 2024):

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

@github-actions[bot] commented on GitHub (Apr 1, 2024): Issues go stale after 21d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.