-
Notifications
You must be signed in to change notification settings - Fork 309
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
what is this error msg? #91
Comments
When this error occurs, some threads on the client get stuck and cannot connect to the server. Both client and server are e7e4cd5 SS server 3.3.4 |
Check the system clocks on your client and server and make sure they are in sync Sent with GitHawk |
router and windows pc and server sync by ntp1.aliyun.com, mobile sync by lte from china mobile now, server change the time zone to beijing, and reboot my vps, let me see..... |
The client and server times are all correct, but there is still this problem, and this error occurs occasionally |
All client and server times are correct, but always got this error |
Do
on both client and server. Are they within +-150s? |
+-2s…… |
Hmm I'll look into this |
|
with bbr2 kernel SS
Cloak
|
Would it be possible to see the full error message in the log? Especially the "received timestamp [xxxxxxxxxxx]" part. I want to see if there's a pattern and compare it with the log timestamp |
i just reboot that vps 1h...there is no error msg now, pls wait... and i remember there is a big numbers like 12345678 with error msg.... anyway,,,, i have 3 client there, pc, mobile, router, shoud i use 3 uid for the test? |
full log, is mobile client... 提前给老哥拜个年,感谢你开发这么横的插件,祝来年一切顺利hah |
Weirdly the log shows that the client has sent the correct timestamp, but it is still identified as outside of the reception window. The code there is quite simple and there are quite a few tests for it. Did this exist in previous versions? Perhaps you could download the binary releases and see if that gives out error as well And 谢谢!很高兴看到这个项目能帮助别人应对网络封锁。鼠年快乐! |
level=warning msg="transport TLS in correct format but not Cloak: timestamp is outside of the accepting window: received timestamp 1579071780" UID="¥¥¥¥¥¥¥¥¥¥¥" encryptionMethod=0 proxyMethod=shadowsocks remoteAddr="¥¥¥¥¥¥¥¥" sessionId=
what is the reason for this?
The text was updated successfully, but these errors were encountered: