mirror of
https://github.com/cbeuw/Cloak.git
synced 2026-04-26 21:15:55 +03:00
[GH-ISSUE #91] what is this error msg？ #80
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Cloak#80
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @qwerttvv on GitHub (Jan 15, 2020).
Original GitHub issue: https://github.com/cbeuw/Cloak/issues/91
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?
@qwerttvv commented on GitHub (Jan 15, 2020):
When this error occurs, some threads on the client get stuck and cannot connect to the server.
Some threads are good.
Both client and server are
e7e4cd5SS server 3.3.4
@cbeuw commented on GitHub (Jan 15, 2020):
Check the system clocks on your client and server and make sure they are in sync
Sent with GitHawk
@qwerttvv commented on GitHub (Jan 15, 2020):
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.....
@qwerttvv commented on GitHub (Jan 19, 2020):
The client and server times are all correct, but there is still this problem, and this error occurs occasionally
@qwerttvv commented on GitHub (Jan 21, 2020):
All client and server times are correct, but always got this error
@cbeuw commented on GitHub (Jan 21, 2020):
Do
on both client and server. Are they within +-150s?
@qwerttvv commented on GitHub (Jan 21, 2020):
+-2s……
@cbeuw commented on GitHub (Jan 21, 2020):
Hmm I'll look into this
@qwerttvv commented on GitHub (Jan 21, 2020):
@qwerttvv commented on GitHub (Jan 21, 2020):
with bbr2 kernel
SS
Cloak
@cbeuw commented on GitHub (Jan 22, 2020):
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
@qwerttvv commented on GitHub (Jan 22, 2020):
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?
@qwerttvv commented on GitHub (Jan 23, 2020):
full log, is mobile client...
but my mobile is always the right time.....
https://github.com/cyqsimon/Cloak-android/releases/tag/v2.1.1.1
https://github.com/shadowsocks/shadowsocks-android/releases/tag/v5.0.2
i will watch more log...just wait
提前给老哥拜个年，感谢你开发这么横的插件，祝来年一切顺利hah
@cbeuw commented on GitHub (Jan 24, 2020):
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 谢谢！很高兴看到这个项目能帮助别人应对网络封锁。鼠年快乐！
@qwerttvv commented on GitHub (Jan 24, 2020):
thx~
i tried v2.1.2 bin,
e7e4cd5my own build, v2.1.3 bin, same error.now,
f90ad52is running