-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Connection dies soon after connecting due to p2p timeout even though I have full cone NAT #6065
Comments
Mine also.. 2024-08-20 10:01:04 2024-08-20T04:31:04.373 DBG ../../eventbus/event_bus.go:101 > Published topic="provider_ping_p2p" event={SessionID:231d338f-4b70-4634-897b-b75b6b5f15b2 Duration:5.000378764s} |
2024-08-20 10:23:12 2024-08-20T04:53:12.544 WRN ../../requests/dialer_swarm.go:293 > Failed to lookup host: "broker.mysterium.network" error="lookup broker.mysterium.network on 192.168.65.7:53: dial udp 192.168.65.7:53: i/o timeout" |
How do you run your node? What parameters are you passing? |
i am just running in docker.. |
what does it means?? --- "timeout waiting for reply to "p2p-keepalive": p2p send timeout" |
It means NAT is not fine. You need full or restricted cone NAT. go for it
…On Sat, Aug 24, 2024 at 16:22 KPBHacker1kk ***@***.***> wrote:
what does it means?? --- *"timeout waiting for reply to "p2p-keepalive":
p2p send timeout"*
—
Reply to this email directly, view it on GitHub
<#6065 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANTPNBYSSAJJKMZDTA4QBDZTCJIRAVCNFSM6AAAAABLIKBR6KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMBYGQYTCNZRGQ>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
timeout waiting for reply to "p2p-keepalive": p2p send timeout
it does work with
--net host
though but im trying not to use it.i have full cone nat
The text was updated successfully, but these errors were encountered: