[GH-ISSUE #5041] error in wiki

gitea-mirror commented

2026-05-05 14:31:21 -06:00

Owner

Copy link

Originally created by @va1dy on GitHub (Nov 1, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/5041

Bug Description

when i try auth.token it says token is wrong and then i try just token(without auth.) it works

frpc Version

0.65.0

frps Version

0.65.0

System Architecture

linux/amd64

Configurations

Logs

with auth.token :

va1dy@debian:/frp_0.65.0_linux_amd64$ ./frpc
WARNING: ini format is deprecated and the support will be removed in the future, please use yaml/json/toml format instead!
2025-11-01 17:28:15.465 [I] [sub/root.go:149] start frpc service for config file [./frpc.ini]
2025-11-01 17:28:15.465 [I] [client/service.go:325] try to connect to server...
2025-11-01 17:28:16.033 [E] [client/service.go:310] token in login doesn't match token from configuration
2025-11-01 17:28:16.033 [W] [client/service.go:328] connect to server error: token in login doesn't match token from configuration
2025-11-01 17:28:16.033 [I] [sub/root.go:167] frpc service for config file [./frpc.ini] stopped
login to the server failed: token in login doesn't match token from configuration. With loginFailExit enabled, no additional retries will be attempted
va1dy@debian:/frp_0.65.0_linux_amd64$

Steps to reproduce

just remove auth. and then it works

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @va1dy on GitHub (Nov 1, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/5041 ### Bug Description when i try auth.token it says token is wrong and then i try just token(without auth.) it works <img width="1041" height="446" alt="Image" src="https://github.com/user-attachments/assets/543e8835-4356-480b-bd82-425621ec3a8f" /> ### frpc Version 0.65.0 ### frps Version 0.65.0 ### System Architecture linux/amd64 ### Configurations <img width="742" height="408" alt="Image" src="https://github.com/user-attachments/assets/91160126-a6b8-466d-aec9-7c0ec2e04aa3" /> ### Logs with auth.token : va1dy@debian:~/frp_0.65.0_linux_amd64$ ./frpc WARNING: ini format is deprecated and the support will be removed in the future, please use yaml/json/toml format instead! 2025-11-01 17:28:15.465 [I] [sub/root.go:149] start frpc service for config file [./frpc.ini] 2025-11-01 17:28:15.465 [I] [client/service.go:325] try to connect to server... 2025-11-01 17:28:16.033 [E] [client/service.go:310] token in login doesn't match token from configuration 2025-11-01 17:28:16.033 [W] [client/service.go:328] connect to server error: token in login doesn't match token from configuration 2025-11-01 17:28:16.033 [I] [sub/root.go:167] frpc service for config file [./frpc.ini] stopped login to the server failed: token in login doesn't match token from configuration. With loginFailExit enabled, no additional retries will be attempted va1dy@debian:~/frp_0.65.0_linux_amd64$ ### Steps to reproduce 1. just remove auth. and then it works 2. 3. ... ### Affected area - [x] Docs - [ ] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:31:21 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:31:24 -06:00

Author

Owner

Copy link

@fatedier commented on GitHub (Nov 2, 2025):

I can’t see your configuration. If it runs correctly, just proceed with your current settings; otherwise, follow the documentation strictly and test step by step.

@fatedier commented on GitHub (Nov 2, 2025): I can’t see your configuration. If it runs correctly, just proceed with your current settings; otherwise, follow the documentation strictly and test step by step.

gitea-mirror commented

2026-05-05 14:31:24 -06:00

Author

Owner

Copy link

@github-actions[bot] commented on GitHub (Nov 17, 2025):

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

@github-actions[bot] commented on GitHub (Nov 17, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

No Branch/Tag specified