github-starred/frp

Fork 0

mirror of https://github.com/fatedier/frp.git synced 2026-05-15 08:05:49 -06:00

[GH-ISSUE #2325] The token does not match after upgrading to version 0.36.2. #1844

New issue

Closed

opened 2026-05-05 13:11:33 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 13:11:33 -06:00

Owner

Originally created by @Dagsi on GitHub (Mar 22, 2021).
Original GitHub issue: https://github.com/fatedier/frp/issues/2325

Originally assigned to: @blizard863 on GitHub.

[REQUIRED] hat version of frp are you using

Version:v0.36.2

[REQUIRED] What operating system and processor architecture are you using
OS:linux_arm64
CPU architecture:

[REQUIRED] description of errors

confile

log file

Steps to reproduce the issue

Stop the program
Replacement program
Re-run, and did not modify the configuration file, but the token does not match.

Supplementary information

Can you guess what caused this issue

Checklist:

[] I included all information required in the sections above
[] I made sure there are no duplicates of this report (Use Search)

Originally created by @Dagsi on GitHub (Mar 22, 2021). Original GitHub issue: https://github.com/fatedier/frp/issues/2325 Originally assigned to: @blizard863 on GitHub.     **[REQUIRED] hat version of frp are you using**  Version:v0.36.2 **[REQUIRED] What operating system and processor architecture are you using** OS:linux_arm64 CPU architecture: **[REQUIRED] description of errors** **confile**  **log file**  **Steps to reproduce the issue** 1. Stop the program 2. Replacement program 3. Re-run, and did not modify the configuration file, but the token does not match. **Supplementary information** **Can you guess what caused this issue** **Checklist**:  - [] I included all information required in the sections above - [] I made sure there are no duplicates of this report [(Use Search)](https://github.com/fatedier/frp/issues?q=is%3Aissue)

gitea-mirror

2026-05-05 13:11:33 -06:00

closed this issue
added the
proposal
label

gitea-mirror commented

2026-05-05 13:11:36 -06:00

Author

Owner

@Dagsi commented on GitHub (Mar 22, 2021):

log file echo:register control error: token in login doesn't match token from configuration

@Dagsi commented on GitHub (Mar 22, 2021): log file echo:register control error: token in login doesn't match token from configuration

gitea-mirror commented

2026-05-05 13:11:37 -06:00

Author

Owner

@blizard863 commented on GitHub (Mar 23, 2021):

what is the versions of your frpc and frps ?

@blizard863 commented on GitHub (Mar 23, 2021): what is the versions of your frpc and frps ?

gitea-mirror commented

2026-05-05 13:11:37 -06:00

Author

Owner

@ViRb3 commented on GitHub (Apr 7, 2021):

I can confirm. The problem is that if you run ./frpc or ./frps without any arguments, it will execute in "cmd mode" instead of "ini mode". If you are in "cmd mode", the token is parsed as an argument from the command line, which in your case is empty. If you explicitly run ./frpc -c fprc.ini or ./frps --config frps.ini, then the correct "ini mode" will be selected, and connection succeeds. I suppose the token mismatch error happens because the client will enter "cmd mode" by default, while the server will enter "ini mode" by default, or vise versa. This is definitely an issue that needs to be cleared though, as it was quite confusing to debug, and a lot of people have the same problem across online forums.

@ViRb3 commented on GitHub (Apr 7, 2021): I can confirm. The problem is that if you run `./frpc` or `./frps` without any arguments, it will execute in "cmd mode" instead of "ini mode". If you are in "cmd mode", the token is parsed as an argument from the command line, which in your case is empty. If you explicitly run `./frpc -c fprc.ini` or `./frps --config frps.ini`, then the correct "ini mode" will be selected, and connection succeeds. I suppose the token mismatch error happens because the client will enter "cmd mode" by default, while the server will enter "ini mode" by default, or vise versa. This is definitely an issue that needs to be cleared though, as it was quite confusing to debug, and a lot of people have the same problem across online forums.

gitea-mirror commented

2026-05-05 13:11:38 -06:00

Author

Owner

@blizard863 commented on GitHub (Apr 7, 2021):

./frpc will use the default value ./frpc.ini
./frps without default file.

@blizard863 commented on GitHub (Apr 7, 2021): ./frpc will use the default value ./frpc.ini ./frps without default file.

gitea-mirror commented

2026-05-05 13:11:39 -06:00

Author

Owner

@ViRb3 commented on GitHub (Apr 7, 2021):

Right, so ./frpc will run in "ini mode", parsing the token from the ini file, while ./frps will run in "cmd mode", not parsing the token, and that's where you get a mismatch error. These are two different default behaviors which is quite confusing in my opinion. Perhaps it's a good idea to make them both "ini by default" or "cmd by default"?

@ViRb3 commented on GitHub (Apr 7, 2021): Right, so `./frpc` will run in "ini mode", parsing the token from the ini file, while `./frps` will run in "cmd mode", not parsing the token, and that's where you get a mismatch error. These are two different default behaviors which is quite confusing in my opinion. Perhaps it's a good idea to make them both "ini by default" or "cmd by default"?

gitea-mirror commented

2026-05-05 13:11:39 -06:00

Author

Owner

@blizard863 commented on GitHub (Apr 8, 2021):

Right, so ./frpc will run in "ini mode", parsing the token from the ini file, while ./frps will run in "cmd mode", not parsing the token, and that's where you get a mismatch error. These are two different default behaviors which is quite confusing in my opinion. Perhaps it's a good idea to make them both "ini by default" or "cmd by default"?

A good point.

@blizard863 commented on GitHub (Apr 8, 2021): > Right, so `./frpc` will run in "ini mode", parsing the token from the ini file, while `./frps` will run in "cmd mode", not parsing the token, and that's where you get a mismatch error. These are two different default behaviors which is quite confusing in my opinion. Perhaps it's a good idea to make them both "ini by default" or "cmd by default"? A good point.