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

cannot connect to peer #14199

Open
garyng2000 opened this issue Jul 9, 2024 · 1 comment
Open

cannot connect to peer #14199

garyng2000 opened this issue Jul 9, 2024 · 1 comment
Labels
Bug Something isn't working

Comments

@garyng2000
Copy link

Describe the bug

I have a private(interop) setup that works generally. But at times, a beacon chain refuses to connect to the defined peers(it worked as it can do the init sync). the log message is just

failed to negotiate security protocol: read tcp4 172.16.0.64:43000->172.16.0.72:33000: wsarecv: An existing connection was forcibly closed by the remote host. peer=16Uiu2HAkyHmP9C8G3k5LxNd1B8pYSxHfcuzbG8sFJwVmdL8oiZQF

or

failed to negotiate security protocol: EOF peer=16Uiu2HAkyHmP9C8G3k5LxNd1B8pYSxHfcuzbG8sFJwVmdL8oiZQF

this happens in both windows version as well as linux(amd64).

and once this happens, it cannot dial that node anymore

Has this worked before in a previous version?

not sure, it works randomly

🔬 Minimal Reproduction

No response

Error

No response

Platform(s)

No response

What version of Prysm are you running? (Which release)

No response

Anything else relevant (validator index / public key)?

No response

@garyng2000 garyng2000 added the Bug Something isn't working label Jul 9, 2024
@garyng2000
Copy link
Author

if I delete the p2p info(metadata and key), it seems to work again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant