mirror of
https://github.com/fatedier/frp.git
synced 2026-05-15 08:05:49 -06:00
[GH-ISSUE #4821] xtcp connection fails despite successful NAT hole punching #3807
Labels
No labels
In Progress
WIP
WaitingForInfo
bug
doc
duplicate
easy
enhancement
future
help wanted
invalid
lifecycle/stale
need-issue-template
need-usage-help
no plan
proposal
pull-request
question
todo
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/frp#3807
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @tsuk1nose on GitHub (May 29, 2025).
Original GitHub issue: https://github.com/fatedier/frp/issues/4821
Bug Description
Issue: xtcp connection fails despite successful NAT hole punching
Problem Description
When attempting to use
xtcpto access a service that works correctly viastcp, the connection fails. Although logs indicate that NAT hole punching is successful, the connection is non-functional and unusable.frpc Version
proxy: 0.60.0; visitor: 0.60.0;
frps Version
0.62.1
System Architecture
server:linux/amd64; proxy:windows/amd64; visitor: windows/amd64;
Configurations
Server Configuration
frps.toml
Client Configuration
Proxy
Visitor
Logs
Logs
Server
Proxy
Visitor
Steps to reproduce
...
Affected area
@fatedier commented on GitHub (May 29, 2025):
frpcandfrpsare the same during testing.debugand check if there are more error logs when the user tries to connect.@tsuk1nose commented on GitHub (May 29, 2025):
Thank you very much for your response and support!
I've now updated all the related packages to version 0.62.1 and also set the log level to debug. Unfortunately, aligning the versions did not resolve the issue. Please find the new debug logs below:
Logs
Server
Proxy
Visitor
@fatedier commented on GitHub (May 29, 2025):
I didn't find anything unusual. You can forward a local nginx HTTP port and use curl to test it, and observe the error message from curl.
@tsuk1nose commented on GitHub (May 29, 2025):
I’ve tested both STCP and XTCP using curl and an Nginx server. STCP works fine, but when using XTCP, I consistently receive the following error:
Curl test results
STCP
XTCP
@fatedier commented on GitHub (May 29, 2025):
The useEncryption and useCompression parameters must be the same on both proxies and visitors.
Since QUIC is encrypted by default, you don't need to set them.
@tsuk1nose commented on GitHub (May 29, 2025):
Ah, that was exactly the issue! The problem is now resolved, and the connection can be established successfully. I guess I’ll have to be a bit more careful with copy-pasting configurations next time 😂
It might be helpful to improve the configuration validation a bit—perhaps the program could throw an error when certain settings are misconfigured by the user.
Thank you so much for taking the time to help me with this.
Have a great day!