Skip to content
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

Open
NinoSkopac opened this issue Jul 22, 2024 · 7 comments
Labels

Comments

@NinoSkopac
Copy link

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

@NinoSkopac NinoSkopac added the bug label Jul 22, 2024
@kpbhaker
Copy link

kpbhaker commented Aug 20, 2024

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:01:04 2024-08-20T04:31:04.374 ERR ../../core/service/session_manager.go:401 > Failed to send p2p keepalive ping. SessionID=231d338f-4b70-4634-897b-b75b6b5f15b2 error="timeout waiting for reply to "p2p-keepalive": p2p send timeout"
2024-08-20 10:01:04 2024-08-20T04:31:04.374 ERR ../../core/service/session_manager.go:404 > Max p2p keepalive err count reached, closing SessionID=231d338f-4b70-4634-897b-b75b6b5f15b2
2024-08-20 10:01:04 2024-08-20T04:31:04.374 INF ../../services/wireguard/service/service.go:163 > Cleaning up session 231d338f-4b70-4634-897b-b75b6b5f15b2
2024-08-20 10:01:04 2024-08-20T04:31:04.374 INF ../../services/wireguard/service/stats_publisher.go:65 > Stopped publishing statistics for session 231d338f-4b70-4634-897b-b75b6b5f15b2

@kpbhaker
Copy link

kpbhaker commented Aug 20, 2024

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"
2024-08-20 10:23:12 2024-08-20T04:53:12.764 DBG ../../session/pingpong/price_calculator.go:52 > Calculated price 35582506040936. Time component: 3.50231504642489101e+13, data component: 5.5935557668844767207e+11. Transferred: 8360, duration: 526.498818151. Price 239475070645145/h, 71842521193543742/GiB
2024-08-20 10:23:12 2024-08-20T04:53:12.804 DBG ../../eventbus/event_bus.go:101 > Published topic="provider_ping_p2p" event={SessionID:b6c2e473-9aa7-4916-8f1c-f4d79e6bf087 Duration:5.000161823s}
2024-08-20 10:23:12 2024-08-20T04:53:12.805 ERR ../../core/service/session_manager.go:401 > Failed to send p2p keepalive ping. SessionID=b6c2e473-9aa7-4916-8f1c-f4d79e6bf087 error="timeout waiting for reply to "p2p-keepalive": p2p send timeout"

@NinoSkopac
Copy link
Author

How do you run your node? What parameters are you passing?

@kpbhaker
Copy link

i am just running in docker..

@kpbhaker
Copy link

what does it means?? --- "timeout waiting for reply to "p2p-keepalive": p2p send timeout"

@NinoSkopac
Copy link
Author

NinoSkopac commented Aug 24, 2024 via email

Copy link

stale bot commented Nov 23, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants