Closed arschlochnop closed 2 years ago
Client error msg:
2022/04/14 18:02:00.232759 ??:1: Check CC response: started
2022/04/14 18:02:00.235739 ??:1: Hello (hellowJjSYfAAGAlnghRIbLbKZodokKqsDlVTEXNsSvoqlMBzMRqGTQGhVTYrlroWvMQiBPpNWSDpNHXDfXTOYZfalwpEWKSDGsVLmf) sent
2022/04/14 18:02:00.241860 ??:1: Hello (hellowJjSYfAAGAlnghRIbLbKZodokKqsDlVTEXNsSvoqlMBzMRqGTQGhVTYrlroWvMQiBPpNWSDpNHXDfXTOYZfalwpEWKSDGsVLmf) timeout
2022/04/14 18:02:00.243417 ??:1: sendHello failed
2022/04/14 18:02:00.241342 ??:1: Hello (hellowJjSYfAAGAlnghRIbLbKZodokKqsDlVTEXNsSvoqlMBzMRqGTQGhVTYrlroWvMQiBPpNWSDpNHXDfXTOYZfalwpEWKSDGsVLmftMh) received
2022/04/14 18:02:00.250198 ??:1: Check CC response: exited
2022/04/14 18:02:00.249150 ??:1: CCMsgTun closed
2022/04/14 18:02:00.251250 ??:1: Collecting system info for checking in
2022/04/14 18:02:00.251793 ??:1: Reading kernel version...
2022/04/14 18:02:01.002804 ??:1: Collected system info, now checking in (https://192.168.126.135:59216/emp3r0r/checkin/8917bef8-24eb-4818-863c-b630b386c16c)
2022/04/14 18:02:01.002804 ??:1: ConnectCC: connecting to https://192.168.126.135:59216/emp3r0r/checkin/8917bef8-24eb-4818-863c-b630b386c16c
2022/04/14 18:02:02.005472 ??:1: Checked in
2022/04/14 18:02:02.005550 ??:1: Checked in on CC: https://192.168.126.135:59216/
2022/04/14 18:02:02.007658 ??:1: ConnectCC: connecting to https://192.168.126.135:59216/emp3r0r/msg/f99d8b2c-60e5-43f6-91e6-8b1ee3997d46
2022/04/14 18:02:03.015331 ??:1: Connected to CC TunAPI
2022/04/14 18:02:03.015382 ??:1: Hearbeat begins
2022/04/14 18:02:03.015382 ??:1: Check CC response: started
2022/04/14 18:02:03.017991 ??:1: Hello (helloGJUOIUKeIlCwSxdKDqlOHsELDxqYoQQhQlxRmKBIzhpWXFjbmocHgHZxmzJFcUzCqSYWLahUhKzDOSIknSknHUJiudgYwBYtwVh) sent
2022/04/14 18:02:03.025280 ??:1: Hello (helloGJUOIUKeIlCwSxdKDqlOHsELDxqYoQQhQlxRmKBIzhpWXFjbmocHgHZxmzJFcUzCqSYWLahUhKzDOSIknSknHUJiudgYwBYtwVh) timeout
2022/04/14 18:02:03.027867 ??:1: sendHello failed
2022/04/14 18:02:03.024758 ??:1: Hello (helloGJUOIUKeIlCwSxdKDqlOHsELDxqYoQQhQlxRmKBIzhpWXFjbmocHgHZxmzJFcUzCqSYWLahUhKzDOSIknSknHUJiudgYwBYtwVhlZRVQU) received
2022/04/14 18:02:03.037363 ??:1: Check CC response: exited
2022/04/14 18:02:03.035807 ??:1: CCMsgTun closed
Testing the latest release below will still have this problem.
1.15.8 (2022-04-11)
2022/04/14 18:02:00.235739 ??:1: Hello (hellowJjSYfAAGAlnghRIbLbKZodokKqsDlVTEXNsSvoqlMBzMRqGTQGhVTYrlroWvMQiBPpNWSDpNHXDfXTOYZfalwpEWKSDGsVLmf) sent
2022/04/14 18:02:00.241860 ??:1: Hello (hellowJjSYfAAGAlnghRIbLbKZodokKqsDlVTEXNsSvoqlMBzMRqGTQGhVTYrlroWvMQiBPpNWSDpNHXDfXTOYZfalwpEWKSDGsVLmf) timeout
2022/04/14 18:02:00.243417 ??:1: sendHello failed
According to this error message, the agent throws a timeout immediately after sending hello, which is odd.
I just tested with current build on Ubuntu 20.04, it works fine though.
Normally it should look like this
@arschlochnop Can you check the timeout
field in ~/.emp3r0r/emp3r0r.json
?
timeout
is a random value generated when you ~/.emp3r0r
is created for the first time, it represents number of milliseconds to wait before marking the handshake as "timeout":
timeout is 0
Well that will be the culprit, did you set it yourself or is it generated automatically?
I didn't customize this file, it should be set automatically.
If you look at https://github.com/jm33-m0/emp3r0r/commit/fe3a0ae01f45b3435265eca7aff328a4ef4fde75 you will find this value should be between 5000 and 10000 when generated automatically.
You can try deleting existing config file and rerun emp3r0r, if the improper value still pops up, please let me know.
I have tested with https://github.com/jm33-m0/emp3r0r/releases/tag/v1.15.8, timeout
is generated as a random number between 5000
and 10000
.
My guess is your config file might be broken before that version.
OS:
Error message:
I recompiled this program: