Hello,
I experienced an interesting behaviour in communication between win client and data proxy.
Client restarted itself because of low traffic - it is normal. Then client got no answer from proxy, so tried the auth process. Proxy blocked the authentication since there already was a connecton with the necessary share code (as for the server).
At the end, I had to intervene and I restarted the client manually.
2021-02-04 23:38:14.4173 [V] Low-traffic detected, restarting client (this is standard behaviour and is safe to ignore)
2021-02-04 23:38:14.4252 [-] Closed TCP connection: 127.0.0.1:31001
2021-02-04 23:38:14.4271 [-] Client restarted successfully
2021-02-04 23:38:14.4527 [-] TCP connection established: 127.0.0.1:31001
2021-02-04 23:52:52.874642 [V] Performing NTP sync (2.planefinder.pool.ntp.org)...
2021-02-04 23:52:52.951867 [V] NTP sync succeeded with settings:
2021-02-04 23:52:52.951913 [V] Stratum: 4
2021-02-04 23:52:52.951929 [V] System clock time: 1612482772.9519
2021-02-04 23:52:52.951948 [V] Corrected clock time: 1612482772.8717
2021-02-04 23:52:52.951957 [V] Corrected clock time: 1612482772.8648 (est)
2021-02-04 23:52:52.951968 [V] NTP drift: -0.0006s/min
2021-02-04 23:52:52.951977 [V] NTP offset: -0.0801s
2021-02-05 00:07:53.313316 [V] Performing NTP sync (2.planefinder.pool.ntp.org)...
2021-02-05 00:07:58.366904 [V] NTP response error, retrying...
2021-02-05 00:07:59.374903 [V] Performing NTP sync (3.planefinder.pool.ntp.org)...
2021-02-05 00:07:59.423555 [V] NTP sync succeeded with settings:
2021-02-05 00:07:59.423602 [V] Stratum: 4
2021-02-05 00:07:59.423615 [V] System clock time: 1612483679.4235
2021-02-05 00:07:59.423625 [V] Corrected clock time: 1612483679.3399
2021-02-05 00:07:59.423634 [V] Corrected clock time: 1612483679.3358 (est)
2021-02-05 00:07:59.423645 [V] NTP drift: -0.0003s/min
2021-02-05 00:07:59.423654 [V] NTP offset: -0.0837s
2021-02-05 00:21:37.674859 [V] 0 byte response received from streaming server: -80
2021-02-05 00:21:37.712086 [-] Disconnected from streaming data proxy server: data-up.planefinder.net:8883
2021-02-05 00:21:37.712124 [V] Attempting TLS: data-up.planefinder.net
2021-02-05 00:21:37.728378 [V] mbedtls_net_connect returned -82
2021-02-05 00:21:37.728442 [!] Failed to connect to streaming data proxy server: data-up.planefinder.net:8883
2021-02-05 00:21:42.741505 [V] Attempting TLS: data-up.planefinder.net
2021-02-05 00:21:42.804113 [V] Performing SSL/TLS handshake...
2021-02-05 00:21:43.24388 [V] SSL/TLS connection successful!
2021-02-05 00:21:43.24418 [-] Connected to streaming data proxy server: data-up.planefinder.net:8883
2021-02-05 00:21:44.67015 [V] Streaming data proxy set authentication status to: Blocked
2021-02-05 00:21:44.67052 [!] Authentication failed with error: Client already connected with this sharecode
2021-02-05 00:21:44.67140 [V] 0 byte response received from streaming server: -30848
2021-02-05 00:21:44.67360 [-] Disconnected from streaming data proxy server: data-up.planefinder.net:8883
2021-02-05 00:22:58.924851 [V] Performing NTP sync (3.planefinder.pool.ntp.org)...
2021-02-05 00:22:59.5164 [V] NTP sync succeeded with settings:
2021-02-05 00:22:59.5230 [V] Stratum: 2
2021-02-05 00:22:59.5245 [V] System clock time: 1612484579.0051
2021-02-05 00:22:59.5257 [V] Corrected clock time: 1612484578.9146
2021-02-05 00:22:59.5268 [V] Corrected clock time: 1612484578.9180 (est)
2021-02-05 00:22:59.5279 [V] NTP drift: -0.0005s/min
2021-02-05 00:22:59.5297 [V] NTP offset: -0.0906s
2021-02-05 00:23:12.974917 [V] Attempting TLS: data-up.planefinder.net
2021-02-05 00:23:13.17486 [V] Performing SSL/TLS handshake...
2021-02-05 00:23:13.255430 [V] SSL/TLS connection successful!
2021-02-05 00:23:13.255483 [-] Connected to streaming data proxy server: data-up.planefinder.net:8883
2021-02-05 00:23:14.307925 [V] Streaming data proxy set authentication status to: Blocked
2021-02-05 00:23:14.307965 [!] Authentication failed with error: Client already connected with this sharecode
2021-02-05 00:23:14.308194 [V] 0 byte response received from streaming server: -30848
2021-02-05 00:23:14.308368 [-] Disconnected from streaming data proxy server: data-up.planefinder.net:8883
(manual restart)
2021-02-05 00:23:50.747682 [-] Closed TCP connection: 127.0.0.1:31001
2021-02-05 00:23:50.747721 [-] Client restarted successfully
2021-02-05 00:23:50.747952 [-] TCP connection established: 127.0.0.1:31001
2021-02-05 00:24:43.101379 [V] Attempting TLS: data-up.planefinder.net
2021-02-05 00:24:43.164469 [V] Performing SSL/TLS handshake...
2021-02-05 00:24:43.381659 [V] SSL/TLS connection successful!
2021-02-05 00:24:43.381691 [-] Connected to streaming data proxy server: data-up.planefinder.net:8883
2021-02-05 00:24:44.434693 [V] Streaming data proxy set authentication status to: Authenticated
...an idea:
This might be an unhandled problem, concerning that the auth attempt came from the same IP.
Generating an unique key for the client when it connects to the server at the very first time may make it easier to decide if it is a duplicated client or it is a valid reauth attempt because there are another problems... Of course, auth attempts shall be limited by a built-in "waiting # secs" cycle - or similar.
...without handling the case, the server would be "hammered" and the client blocked.