[GH-ISSUE #3159] How to judge the failure of xtcp, and then automatically convert to stcp #2530

New issue

Closed

opened 2026-05-05 13:37:50 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

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

Owner

Originally created by @aotuitx on GitHub (Nov 3, 2022).
Original GitHub issue: https://github.com/fatedier/frp/issues/3159

How to judge the failure of xtcp, and then automatically convert to stcp?

How is the v2 version now? Can you see it this year?

Originally created by @aotuitx on GitHub (Nov 3, 2022). Original GitHub issue: https://github.com/fatedier/frp/issues/3159 How to judge the failure of xtcp, and then automatically convert to stcp? How is the v2 version now? Can you see it this year?

gitea-mirror

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

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Dec 4, 2022):

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

@github-actions[bot] commented on GitHub (Dec 4, 2022): Issues go stale after 30d of inactivity. Stale issues rot after an additional 7d of inactivity and eventually close.

gitea-mirror commented

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

Author

Owner

@Bellegar commented on GitHub (Apr 26, 2023):

I assumed that automatic fallback to stcp from xtcp is mentioned in readme "You might want to fallback to stcp if xtcp doesn't work." (as protocol ICE works STUN->TURN), suddenly, it's not woking as i expected.

@Bellegar commented on GitHub (Apr 26, 2023): I assumed that automatic fallback to stcp from xtcp is mentioned in readme "You might want to fallback to stcp if xtcp doesn't work." (as protocol ICE works STUN->TURN), suddenly, it's not woking as i expected.