[GH-ISSUE #4786] 这种情况下，如何让失败退出程序？ #3779

New issue

Closed

opened 2026-05-05 14:25:17 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 14:25:17 -06:00

Owner

Originally created by @wuai1024 on GitHub (May 6, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4786

Describe the feature request

域名绑定的ip发生变更后，frpc就会这样无限重连，不会重新解析域名连接，必须得重启后才会去解析域名的最新ip连接。

Describe alternatives you've considered

希望这时候能直接退出

Originally created by @wuai1024 on GitHub (May 6, 2025). Original GitHub issue: https://github.com/fatedier/frp/issues/4786 ### Describe the feature request 域名绑定的ip发生变更后，`frpc`就会这样无限重连，不会重新解析域名连接，必须得重启后才会去解析域名的最新ip连接。 ![Image](https://github.com/user-attachments/assets/fdd17346-c309-4d5c-8c4a-e7ff7dcbf7fd) ### Describe alternatives you've considered 希望这时候能直接退出

gitea-mirror

2026-05-05 14:25:17 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

@wuai1024 commented on GitHub (May 15, 2025):

？？？

@wuai1024 commented on GitHub (May 15, 2025): ？？？

gitea-mirror commented

2026-05-05 14:25:22 -06:00

Author

Owner

@wuai1024 commented on GitHub (May 15, 2025):

有解决办法吗？现在是加了个智能插座，当 ddns 域名更新后，发现连接不上了，就用插座重启整个设备，让frpc重新连接。这样很麻烦。也不智能。

@wuai1024 commented on GitHub (May 15, 2025): 有解决办法吗？现在是加了个智能插座，当 ddns 域名更新后，发现连接不上了，就用插座重启整个设备，让frpc重新连接。这样很麻烦。也不智能。

gitea-mirror commented

2026-05-05 14:25:22 -06:00

Author

Owner

@litrycn commented on GitHub (May 21, 2025):

conf/frpc_full_example.toml

# Decide if exit program when first login failed, otherwise continuous relogin to frps
# default is true
loginFailExit = true

@litrycn commented on GitHub (May 21, 2025): # conf/frpc_full_example.toml ``` # Decide if exit program when first login failed, otherwise continuous relogin to frps # default is true loginFailExit = true ```

gitea-mirror commented

2026-05-05 14:25:23 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Jun 5, 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 (Jun 5, 2025): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

gitea-mirror referenced this issue

2026-05-05 14:49:29 -06:00

[PR #3779] [MERGED] update for strict config #4827

gitea-mirror referenced this issue

2026-05-05 14:49:51 -06:00

[PR #3845] [MERGED] bump version to v0.53.0 #4845