-
Enthusiast
[FIX] Time synchronization poorness caused to block connection
I've noticed that this error is caused by running a mu server from a vps host, its a common bug for certain hypervisors (KVM in my case). it is a hardware issue and there is no OS-side fix for it.
the solutioni is to email your provider's support and ask for them to switch your vps' CPUCOUNT to 1, It is a simple request and will be quickly granted. This has fixed the issue for me.
It's racked my brain for over a month, so I hope it helps everyone with the same issue!
-
-
Apprentice
Re: [FIX] Time synchronization poorness caused to block connection
that does not fix my problem, i have the same error:
23:17:45 (sebasn)(seBax) Time synchronization poorness caused to block connection -7160
[Close Client][0] Call to Close Client of seBax
WSARecv() failed with error 10038
Appreciate your help.
-
Enthusiast
Re: [FIX] Time synchronization poorness caused to block connection
sorry but thas how my problem was fixed. maybe have your provider verify that is has been changed and try hard resetting your server