Can't connect from a 2020.1.4 to a 2020.1.3

Hi Mike,

This might be indicative of a problem with the underlying peer-to-peer transport protocol, since 2020.1.4 removed support for one of the deprecated protocols. 2020.1.3 supports both but fallbacks to the old one, even if the newer one should always work. In all cases, we would need logs from both the client and server to diagnose the issue. You can follow the same instructions from this thread (https://forum.devolutions.net/topics/33468/wayk-now-frequently-disconnects-during-use#138561).

I'm repeating the steps from my colleague Richard here:

On the client (the machine you connect *from*), please take the following steps:

• Go to Options > Advanced, and adjust the logging level to "Debug"
• Close Wayk Now completely, and re-open it again
• Reproduce the issue on the client
• Finally, send us the log file from %AppData%\Wayk\logs\WaykNow.log

As for the server, the procedure is the same, except the log file is located in %ProgramData%\Wayk\logs\NowService.log

It's a stretch, but I thought I would ask: are any of the client or server system clock time incorrect? The only case of a failure with the newer protocol I ever observed at this point was with a system that had an incorrect system clock (wrong system time configured), that would cause timestamp validation failures and prevent the connection from happening.

Best regards,

Hi,

We just made a change that should fix your issue. Could you try again please and let us know if it works now with the latest version, 2020.1.4 ?

Thanks and sorry for the inconvenience
Best regards,

On my 2020.1.4 I closed it and reopened it and attempted to connect to 2020.1.3 and got the same results

No problem going from 2020.1.3 to 2020.1.3

Hi Mike,

In that case, we would need logs from both the client and server to diagnose the issue. It is probably something else and we can't figure it out without logs. If you could send us logs, it would be very helpful.

Thanks in advance
Best regards,

Here are 3 log files
the PC is the 2020-1-4 and the other 2 are on a MACs and are both 2020-1-3

Hi Mike,

We can see from the logs that the Wayk Now server is unable to make a call to our relay service, https://api.jet-relay.net

We've seen intermittent failures like this one, but we couldn't pinpoint the core underlying issue yet. In your case, the problem appears to be consistently happening, so it may be something different that is causing it.

Do you enforce proxy usage, and if so, does it also enforce https traffic inspection?

Can you open the following URLs correctly (it should show a short message to say that it is working):
https://api.jet-relay.net/health
https://devolutions-jet-0-10-0-prd-eus-1.jet-relay.net/health

I noticed from the logs that it can fallback to the older peer-to-peer protocol that uses the same relay servers, but without https/443, only TCP/8080, so connectivity appears to be partially working, and the issue would be limited to the initial https control call to our relay servers.

Best regards,

I'll submit those 2 sites to LightSpeed Relay to make them allowed. It will take a few hours to test it