[GH-ISSUE #1574] Feature suggestion: should FRPC report its version to FRPS for compatibility check? #1248

New issue

Closed

opened 2026-05-05 12:47:54 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 12:47:54 -06:00

Owner

Originally created by @keyoti on GitHub (Dec 21, 2019).
Original GitHub issue: https://github.com/fatedier/frp/issues/1574

For my use it would be helpful if FRPC sent its version to FRPS. If the FRPC version is too old, then FRPS sends a message back like "Your FRPC client is too old, please update it".

I would suggest in frps.ini

[common]
oldest_supported_client_version = 0.30

I guess you don't want to do a lot of backwards compatibility testing, which is fine, but at least this would provide a way to force clients to update.

Should I try to do a PR?

Originally created by @keyoti on GitHub (Dec 21, 2019). Original GitHub issue: https://github.com/fatedier/frp/issues/1574 For my use it would be helpful if FRPC sent its version to FRPS. If the FRPC version is too old, then FRPS sends a message back like "Your FRPC client is too old, please update it". I would suggest in frps.ini ``` [common] oldest_supported_client_version = 0.30 ``` I guess you don't want to do a lot of backwards compatibility testing, which is fine, but at least this would provide a way to force clients to update. Should I try to do a PR?

gitea-mirror closed this issue

2026-05-05 12:47:56 -06:00

gitea-mirror commented

2026-05-05 12:47:57 -06:00

Author

Owner

@fatedier commented on GitHub (Jan 5, 2020):

We already have the check on https://github.com/fatedier/frp/blob/master/utils/version/version.go#L50

It's compatible since v0.18.0 and i will keep it backwards compatible as far as possible.

@fatedier commented on GitHub (Jan 5, 2020): We already have the check on https://github.com/fatedier/frp/blob/master/utils/version/version.go#L50 It's compatible since v0.18.0 and i will keep it backwards compatible as far as possible.