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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reports of Windows users losing peers #13431
Comments
welp my system worked fine for 3 years and now I lose all peers after about 2 hours, had to setup a schedule task to kill and restart beacon every 2 hours.. solution below!! |
i'll try to add this to the docs |
closing issue with added docs now |
welp guess i spoke to soon. back to the same problem. it worked for 2-3 days then stopped. I rebooted my router / modem and same thing worked for a day.. I'm really at my wits end. can't understand how when i stop and restart beacon it works for a few hours then stops. its maddening. |
Same issue. I have a Windows 10 and a Windows 11 PC. The beacon client running on them loses peers after a few hours. I sync the Windows time every 5 minutes but it does not work. They had been working fine for months. I guess the issue became prominent since the Dencun upgrade. |
following.. please let me know if you find out anything.. It seems like something they did around December really made it bad for windows users.. I would love to switch to a minority client but just haven't had the time to figure it out.. can you add your comment to this new issue i opened? #13936 thanks! |
Yes, I did found a workaround:
|
thanks so much for the workaround! i've been suffering for months lol.. at least now I know I'm not crazy and this is definitely a real issue.. lighthouse here we come |
i'm very confused because I'm using nethermind (i gave up on geth).. can you give me specific steps on how to migrate from prysm to lighthouse using nethermind? thanks! |
It's basically the same as running prysm, here is my script. You might need to sync from genesis. |
馃拵 Issue
Background
Opening this as it's nuanced and haven't been wide spread however it does randomly happen to some windows users
where the OS decides to drop all packets from prysm for some reason. This results in a reduced peer count. Root cause is currently unknown but opening this as a tracking issue.
related prysmaticlabs/documentation#891
related #8144
The text was updated successfully, but these errors were encountered: