Forum / Wayk Now - Support

3.3.2.0 stays minimized and unresponsive?

  • Create an Issue
  • Cancel

I upgraded Wayk Now yesterday on a couple of my machines, at first they seemed to be fine, but either after minimizing the main window or some time the main window would go away. If I tried to open Wayk nothing would happen, if I clicked the icon in the notification area same thing, nothing. Tried reinstalling and again would work for a few minutes, but then the window would close and nothing.

Clock23 days

Hi,

This is definitely odd. Can you enable logs as described in https://forum.devolutions.net/topic32458-i-cannot-connect-to-my-remote-machine.aspx#post132281 and either post them here or send them to support@devolutions.net?

Best regards,

Marc-André Moreau

signaturesignature

Clock23 days

2019-09-21 12:39:31 NowService::main [INFO] - service started
2019-09-21 12:39:31 NowService::main [INFO] - called with args: ["WaykNowService"]
2019-09-21 12:39:31 common::logging [DEBUG] - socket listening on ipc://wayk_session_control
2019-09-21 12:39:31 common::logging [DEBUG] - socket listening on ipc://wayk_service_control
2019-09-21 12:39:31 NowService::main [INFO] - ipc services started
2019-09-21 12:39:31 common::logging [DEBUG] - [0] Address: 127.0.0.1 Broadcast: 0.0.0.0 Netmask: 255.0.0.0 up p2p: 0 lo: 1 bcast: 0 mcast: 1
2019-09-21 12:39:31 common::logging [DEBUG] - [1] Address: 192.168.1.148 Broadcast: 255.255.255.255 Netmask: 255.255.255.0 up p2p: 0 lo: 0 bcast: 1 mcast: 1
2019-09-21 12:39:31 common::logging [DEBUG] - [2] Address: 10.4.10.6 Broadcast: 255.255.255.255 Netmask: 255.255.255.252 up p2p: 0 lo: 0 bcast: 1 mcast: 1
2019-09-21 12:39:31 common::logging [DEBUG] - [3] Address: 192.168.56.1 Broadcast: 255.255.255.255 Netmask: 255.255.255.0 up p2p: 0 lo: 0 bcast: 1 mcast: 1
2019-09-21 12:39:31 common::logging [DEBUG] - [0] Address: 127.0.0.1 Broadcast: 0.0.0.0 Netmask: 255.0.0.0 up p2p: 0 lo: 1 bcast: 0 mcast: 1
2019-09-21 12:39:31 common::logging [DEBUG] - [1] Address: 192.168.1.148 Broadcast: 255.255.255.255 Netmask: 255.255.255.0 up p2p: 0 lo: 0 bcast: 1 mcast: 1
2019-09-21 12:39:31 common::logging [DEBUG] - [2] Address: 10.4.10.6 Broadcast: 255.255.255.255 Netmask: 255.255.255.252 up p2p: 0 lo: 0 bcast: 1 mcast: 1
2019-09-21 12:39:31 common::logging [DEBUG] - [3] Address: 192.168.56.1 Broadcast: 255.255.255.255 Netmask: 255.255.255.0 up p2p: 0 lo: 0 bcast: 1 mcast: 1
2019-09-21 12:39:31 common::logging [DEBUG] - Listening on 192.168.1.148:4489/TCP
2019-09-21 12:39:31 common::logging [DEBUG] - Listening on 10.4.10.6:4489/TCP
2019-09-21 12:39:31 common::logging [DEBUG] - Listening on 192.168.56.1:4489/TCP
2019-09-21 12:39:31 NowService::main [DEBUG] - entering service loop
2019-09-21 12:39:31 NowService::service [DEBUG] - den_client_on_state_change called - state=CONNECTING
2019-09-21 12:39:33 common::logging [DEBUG] - Connecting to wss://den.wayk.net:443/
2019-09-21 12:39:33 common::logging [DEBUG] - resolved 40.117.148.14 for den.wayk.net
2019-09-21 12:39:34 common::logging [DEBUG] - HTTP/1.1 101 Switching Protocols
2019-09-21 12:39:34 common::logging [DEBUG] - Connection: Upgrade
2019-09-21 12:39:34 common::logging [DEBUG] - Upgrade: websocket
2019-09-21 12:39:34 common::logging [DEBUG] - Sec-WebSocket-Accept: bGEX35LzulFFBITslKxZcuyE0vg=
2019-09-21 12:39:34 common::logging [DEBUG] - Strict-Transport-Security: max-age=15768000
2019-09-21 12:39:34 common::logging [INFO] - << Handshake Response
2019-09-21 12:39:35 common::logging [INFO] - << Register Response
2019-09-21 12:39:35 common::logging [INFO] - Iface "DenServer" id: 2 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - {
2019-09-21 12:39:35 common::logging [INFO] - Proc "Handshake" id: 1 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "GetId" id: 6 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "GetCaChain" id: 7 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "RequestCertificate" id: 8 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "Terminate" id: 2 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "SessionInitiate" id: 3 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "SessionTerminate" id: 4 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "SessionGetIceServers" id: 5 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - }
2019-09-21 12:39:35 common::logging [INFO] - Iface "DenPeer" id: 3 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - {
2019-09-21 12:39:35 common::logging [INFO] - Proc "SessionHandshake" id: 1 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "SessionExchange" id: 2 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - }
2019-09-21 12:39:35 common::logging [INFO] - Iface "DenClient" id: 1 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - {
2019-09-21 12:39:35 common::logging [INFO] - Proc "SessionInitiate" id: 1 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - Proc "SessionTerminate" id: 2 flags: 0x1000
2019-09-21 12:39:35 common::logging [INFO] - }
2019-09-21 12:39:35 common::logging [INFO] - Connected to rpc server
2019-09-21 12:39:35 common::logging [INFO] - Resolving "den"
2019-09-21 12:39:35 common::logging [INFO] - << Resolve Response
2019-09-21 12:39:35 common::logging [INFO] - Resolved "den" -> (0xAD1CAE4B) in 281 ms
2019-09-21 12:39:35 common::logging [INFO] - Binding DenServer interface (ifaceId=2, clientId=0xAD1C8AC5, serverId=0xAD1CAE4B)
2019-09-21 12:39:35 common::logging [INFO] - << Bind Response
2019-09-21 12:39:35 common::logging [INFO] - Bound DenServer interface (ifaceId=2, clientId=0xAD1C8AC5, serverId=0xAD1CAE4B)
2019-09-21 12:39:35 common::logging [INFO] - Calling DenServer::Handshake (callId=1)
2019-09-21 12:39:36 common::logging [INFO] - << Result Response
2019-09-21 12:39:36 common::logging [INFO] - Result DenServer::Handshake (callId=1, 312 ms)
2019-09-21 12:39:37 common::logging [DEBUG] - Certificate can't be loaded.
2019-09-21 12:39:37 common::logging [DEBUG] - No certificate: Machine is not registered.
2019-09-21 12:39:38 common::logging [INFO] - Http msg... (callId=0).
2019-09-21 12:39:39 common::logging [INFO] - << HTTP Response
2019-09-21 12:39:39 common::logging [INFO] - Http message (callId=0) succeeded in 610 ms
2019-09-21 12:39:39 common::logging [WARN] - NowDen_Register: No JSON body returned. Probably an old server.
2019-09-21 12:39:39 common::logging [DEBUG] - Identity after Register 780860 (e6735e12-99f1-4272-ae47-6325296fdb2c)
2019-09-21 12:39:39 common::logging [INFO] - Verify msg... (callId=1).
2019-09-21 12:39:40 common::logging [INFO] - << Verify Response
2019-09-21 12:39:40 common::logging [INFO] - Verify message (callId=1) succeeded in 750 ms
2019-09-21 12:39:41 common::logging [INFO] - ipify: 212.92.120.228
2019-09-21 12:39:41 common::logging [INFO] - Calling DenServer::GetCaChain (callId=2)
2019-09-21 12:39:42 common::logging [INFO] - << Result Response
2019-09-21 12:39:42 common::logging [INFO] - Result DenServer::GetCaChain (callId=2, 547 ms)
2019-09-21 12:39:42 NowService::service [DEBUG] - den_client_on_state_change called - state=CONNECTED
2019-09-21 12:39:42 NowService::service [INFO] - Source ID: 780860

Clock23 days

Your service logs look fine, can you enable the main application logs following the instructions at https://helpwayk.devolutions.net/kb_logs.htm ?

Set the log level to INFO, it should reveal a bit more. The log file is located in %Appdata%/Wayk/logs

Marc-André Moreau

signaturesignature

Clock23 days

[2019-09-21] [17:04:51:309] [13308:00003c10] [DEBUG][WebPki] - NowWebPki_Init: loaded 57 CA certs from Windows
[2019-09-21] [17:04:51:314] [13308:00003c10] [DEBUG][WebPki] - NowWebPki_Init: loaded embedded CA bundle
[2019-09-21] [17:04:51:390] [13308:00003c10] [DEBUG][NowSocket] - [0] Address: 127.0.0.1 Broadcast: 0.0.0.0 Netmask: 255.0.0.0 up p2p: 0 lo: 1 bcast: 0 mcast: 1
[2019-09-21] [17:04:51:390] [13308:00003c10] [DEBUG][NowSocket] - [1] Address: 192.168.1.148 Broadcast: 255.255.255.255 Netmask: 255.255.255.0 up p2p: 0 lo: 0 bcast: 1 mcast: 1
[2019-09-21] [17:04:51:390] [13308:00003c10] [DEBUG][NowSocket] - [2] Address: 192.168.56.1 Broadcast: 255.255.255.255 Netmask: 255.255.255.0 up p2p: 0 lo: 0 bcast: 1 mcast: 1
[2019-09-21] [17:04:51:532] [13308:000044e8] [DEBUG][NowNngChannel] - pipe event NNG_PIPE_EV_ADD_PRE (ipc://wayk_service_control [D})
[2019-09-21] [17:04:51:532] [13308:000044e8] [DEBUG][NowNngChannel] - pipe event NNG_PIPE_EV_ADD_POST (ipc://wayk_service_control [D})
[2019-09-21] [17:04:51:532] [13308:000044e8] [DEBUG][NowService] - Fetching current state of channels
[2019-09-21] [17:04:51:534] [13308:0000440c] [DEBUG][NowService] - NowService_UpdateDenState: 3 - 780860 - wss://den.wayk.net
[2019-09-21] [17:04:51:652] [13308:000040a8] [DEBUG][CowRpc] - Connecting to wss://den.wayk.net:443/
[2019-09-21] [17:04:51:658] [13308:000040a8] [DEBUG][NowNameResolver] - resolved 40.117.148.14 for den.wayk.net
[2019-09-21] [17:04:51:774] [13308:000040a8] [DEBUG][NowWebSocket] - HTTP/1.1 101 Switching Protocols
[2019-09-21] [17:04:51:774] [13308:000040a8] [DEBUG][NowWebSocket] - Connection: Upgrade
[2019-09-21] [17:04:51:774] [13308:000040a8] [DEBUG][NowWebSocket] - Upgrade: websocket
[2019-09-21] [17:04:51:774] [13308:000040a8] [DEBUG][NowWebSocket] - Sec-WebSocket-Accept: yAVA5oTz/8HnRk8wQ/Y/gc5I2Sc=
[2019-09-21] [17:04:51:774] [13308:000040a8] [DEBUG][NowWebSocket] - Strict-Transport-Security: max-age=15768000
[2019-09-21] [17:04:51:804] [13308:000040a8] [INFO][CowRpc] - << Handshake Response
[2019-09-21] [17:04:51:899] [13308:000044e8] [DEBUG][NowService] - Fetching current state of sharer
[2019-09-21] [17:04:51:899] [13308:000044e8] [DEBUG][NowService] - Fetching current state of access control
[2019-09-21] [17:04:51:900] [13308:00003c10] [DEBUG][NowNngChannel] - socket dialed ipc://wayk_service_control
[2019-09-21] [17:04:51:900] [13308:00003c10] [DEBUG][NowService] - Fetching current state of sharer
[2019-09-21] [17:04:51:925] [13308:000040a8] [INFO][CowRpc] - << Register Response
[2019-09-21] [17:04:51:925] [13308:000040a8] [INFO][CowRpcProto] - Iface "DenServer" id: 2 flags: 0x1000
[2019-09-21] [17:04:51:925] [13308:000040a8] [INFO][CowRpcProto] - {
[2019-09-21] [17:04:51:925] [13308:000040a8] [INFO][CowRpcProto] - Proc "Handshake" id: 1 flags: 0x1000
[2019-09-21] [17:04:51:925] [13308:000040a8] [INFO][CowRpcProto] - Proc "GetId" id: 6 flags: 0x1000
[2019-09-21] [17:04:51:925] [13308:000040a8] [INFO][CowRpcProto] - Proc "GetCaChain" id: 7 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "RequestCertificate" id: 8 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "Terminate" id: 2 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "SessionInitiate" id: 3 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "SessionTerminate" id: 4 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "SessionGetIceServers" id: 5 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - }
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Iface "DenPeer" id: 3 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - {
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "SessionHandshake" id: 1 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "SessionExchange" id: 2 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - }
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Iface "DenClient" id: 1 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - {
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "SessionInitiate" id: 1 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - Proc "SessionTerminate" id: 2 flags: 0x1000
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpcProto] - }
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][NowDen] - Connected to rpc server
[2019-09-21] [17:04:51:926] [13308:000040a8] [INFO][CowRpc] - Resolving "den"
[2019-09-21] [17:04:51:959] [13308:0000481c] [INFO][CowRpc] - << Resolve Response
[2019-09-21] [17:04:51:959] [13308:000040a8] [INFO][CowRpc] - Resolved "den" -> (0xE3C27FCD) in 32 ms
[2019-09-21] [17:04:51:959] [13308:000040a8] [INFO][CowRpcBind] - Binding DenServer interface (ifaceId=2, clientId=0xE3C256D8, serverId=0xE3C27FCD)
[2019-09-21] [17:04:52:005] [13308:0000481c] [INFO][CowRpc] - << Bind Response
[2019-09-21] [17:04:52:005] [13308:000040a8] [INFO][CowRpcBind] - Bound DenServer interface (ifaceId=2, clientId=0xE3C256D8, serverId=0xE3C27FCD)
[2019-09-21] [17:04:52:005] [13308:000040a8] [INFO][CowRpc] - Calling DenServer::Handshake (callId=1)
[2019-09-21] [17:04:52:028] [13308:0000481c] [INFO][CowRpc] - << Result Response
[2019-09-21] [17:04:52:028] [13308:000040a8] [INFO][CowRpc] - Result DenServer::Handshake (callId=1, 32 ms)
[2019-09-21] [17:04:52:462] [13308:000040a8] [DEBUG][NowDen] - Certificate can't be loaded.
[2019-09-21] [17:04:52:472] [13308:000040a8] [DEBUG][NowDen] - No certificate: Machine is not registered.
[2019-09-21] [17:04:53:412] [13308:000040a8] [INFO][CowRpc] - Http msg... (callId=0).
[2019-09-21] [17:04:53:890] [13308:0000481c] [INFO][CowRpc] - << HTTP Response
[2019-09-21] [17:04:53:890] [13308:000040a8] [INFO][CowRpc] - Http message (callId=0) succeeded in 484 ms
[2019-09-21] [17:04:53:890] [13308:000040a8] [WARN][NowDen] - NowDen_Register: No JSON body returned. Probably an old server.
[2019-09-21] [17:04:53:892] [13308:000040a8] [DEBUG][NowDen] - Identity after Register 176332 (7ab1155a-db8f-4fe7-b8e6-8d684c08177f)
[2019-09-21] [17:04:53:892] [13308:00003c10] [DEBUG][NowService] - Fetching current state of sharer
[2019-09-21] [17:04:53:895] [13308:000040a8] [INFO][CowRpc] - Verify msg... (callId=1).
[2019-09-21] [17:04:53:933] [13308:0000481c] [INFO][CowRpc] - << Verify Response
[2019-09-21] [17:04:53:933] [13308:000040a8] [INFO][CowRpc] - Verify message (callId=1) succeeded in 47 ms
[2019-09-21] [17:04:54:077] [13308:000040a8] [INFO][NowNat] - ipify: 71.174.119.140
[2019-09-21] [17:04:54:082] [13308:000040a8] [INFO][CowRpc] - Calling DenServer::GetCaChain (callId=2)
[2019-09-21] [17:04:54:379] [13308:0000481c] [INFO][CowRpc] - << Result Response
[2019-09-21] [17:04:54:379] [13308:000040a8] [INFO][CowRpc] - Result DenServer::GetCaChain (callId=2, 296 ms)
[2019-09-21] [17:05:12:743] [13308:00003c10] [DEBUG][NowService] - Fetching current state of sharer
[2019-09-21] [17:05:12:780] [13308:00003c10] [INFO][CowRpcBind] - Unbinding DenServer interface (ifaceId=2, clientId=0xE3C256D8, serverId=0xE3C27FCD)
[2019-09-21] [17:05:12:936] [13308:0000481c] [INFO][CowRpc] - << Unbind Response
[2019-09-21] [17:05:12:936] [13308:00003c10] [INFO][CowRpcBind] - Unbound DenServer interface (ifaceId=2, clientId=0xE3C256D8, serverId=0xE3C27FCD)
[2019-09-21] [17:05:12:962] [13308:0000481c] [INFO][CowRpc] - << Terminate Response
[2019-09-21] [17:05:12:964] [13308:0000024c] [DEBUG][NowNngChannel] - aio was cancelled
[2019-09-21] [17:05:12:964] [13308:0000440c] [DEBUG][NowNngChannel] - received a stop message
[2019-09-21] [17:05:12:965] [13308:000024a8] [DEBUG][NowNngChannel] - pipe event NNG_PIPE_EV_REM_POST (ipc://wayk_service_control [D})
[2019-09-21] [17:05:12:965] [13308:000024a8] [DEBUG][NowService] - NowService_UpdateDenState: 5 - (nil) - (nil)

Clock23 days

Hello

Your description and logs appear similar to a known regression that affected some users on 3.2.2.

That issue specifically occurs when exiting the Wayk Now client application. Can you clarify if the freezing happens when you exit the client application, or at another time(s)?

Thanks and kind regards,

Richard Markievicz

signaturesignature

Clock22 days

I had one of my computers that it appeared to freeze on it's own, but I haven't been able to replicate it. Every other instance froze when I tried to exit the software

Clock22 days

Hello

Thanks for the further information.

The Wayk Now client executable and the Windows service component share a communication channel between one another, to share state information and drive UI functionality from the service-side. The issue specifically occurs when that communication channel is closed - which most normally happens when exiting the client, although there are other circumstances that could cause it too.

We have implemented a fix for that in the next release, although currently I don't have a date that it will be available.

In the meantime, you should be able to largely avoid the issue by leaving the Wayk Now client running. You can also temporarily downgrade to 3.3.1, unless there is specific functionality you need in 3.3.2. Here is the download link for the 3.3.1 x64 installer.

I do apologize for the inconvenience caused.

Thanks and kind regards,

Richard Markievicz

signaturesignature

Clock22 days