Jump to content
Get SynergyOpen a support ticket

SSL Encryption Makes Client lag


Recommended Posts

Guest Andrew Nelless

Hi folks,

We have not been able to reproduce the case where turning on SSL produces lag, although we have bee aware of it for sometime. Unfortunately DEBUG1 lacks enough information to diagnose low level networking issues, but switching to DEBUG2 likely won't help either to the 1 second log granularity.

I'm going to increase granularity of the log timestamps in 1.9 for you guys, and we'll see if we can narrow it down.

Link to post
Share on other sites
gdawg0203
On 5/16/2017 at 1:39 AM, Nick Bolton said:

@Paul Suarez I think this is an issue with our actual SSL implementation and not the network.

@Jerry Hou Are you able to reproduce this bug?

From what I just saw from using Synergy without SSL encryption it will on occasion just start lagging behind when I launch an application (chrome, word, documents) but doesn't do it as bad as when  SSL encryption is turned on. It may just be an issue with the client (being a surface with 8GB of ram and the i-5 processor) I'll just have to wait and see if the next update fixes it.

Link to post
Share on other sites
On 5/16/2017 at 7:08 AM, Andrew Nelless said:

Hi folks,

We have not been able to reproduce the case where turning on SSL produces lag, although we have bee aware of it for sometime. Unfortunately DEBUG1 lacks enough information to diagnose low level networking issues, but switching to DEBUG2 likely won't help either to the 1 second log granularity.

I'm going to increase granularity of the log timestamps in 1.9 for you guys, and we'll see if we can narrow it down.

Any update regarding this or should I ask for a refund?

Link to post
Share on other sites
Guest Andrew Nelless

Hi @ga$E

Apologies regarding this. There are a few high priority issues blocking the v1.9 release. We're currently looking in the 2 week timeframe. Improved logging is definitely on the agenda short term, but I can't promise that we'll be able to reproduce or solve this SSL issue in v1.9.0

If you're uncomfortable leaving SSL off, we'd be happy to offer you a refund, but we'd definitely like to keep you onboard so we can get this solved.

Link to post
Share on other sites

I am having the same issue but much worse as I am going over company VPN from work laptop to my home computer (Using port forwarding).

[2017-05-25T11:26:21] ERROR: ssl error occurred (generic failure)

[2017-05-25T11:26:21] ERROR: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

[2017-05-25T11:26:21] ERROR: failed to accept secure socket

[2017-05-25T11:26:21] INFO: client connection may not be secure

 

Both computers are running Win10 and are wired and running 1.8.8...

Edited by midakin
Link to post
Share on other sites

Nope both are enabled. It initially accepts then fails repeatedly after....

 

[2017-05-26T08:32:46] NOTE: started server, waiting for clients

[2017-05-26T08:32:46] INFO: watchdog status: ok

[2017-05-26T08:32:47] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-26T08:32:47] INFO: accepted secure socket

[2017-05-26T08:32:47] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD

[2017-05-26T08:32:47] NOTE: accepted client connection

[2017-05-26T08:32:48] NOTE: client "x-x" has connected

[2017-05-26T08:32:49] INFO: switch from "x-1" to "x-x" at 3519,689

[2017-05-26T08:32:49] INFO: leaving screen

[2017-05-26T08:32:49] INFO: screen "x-1" updated clipboard 0

1

[2017-05-26T08:33:02] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-26T08:33:02] ERROR: ssl error occurred (generic failure)

[2017-05-26T08:33:02] ERROR: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

[2017-05-26T08:33:02] ERROR: failed to accept secure socket

[2017-05-26T08:33:02] INFO: client connection may not be secure

[2017-05-26T08:33:18] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-26T08:33:18] ERROR: ssl error occurred (generic failure)

[2017-05-26T08:33:18] ERROR: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

[2017-05-26T08:33:18] ERROR: failed to accept secure socket

[2017-05-26T08:33:18] INFO: client connection may not be secure

Link to post
Share on other sites
On 5/25/2017 at 0:15 PM, Andrew Nelless said:

Hi @ga$E

Apologies regarding this. There are a few high priority issues blocking the v1.9 release. We're currently looking in the 2 week timeframe. Improved logging is definitely on the agenda short term, but I can't promise that we'll be able to reproduce or solve this SSL issue in v1.9.0

If you're uncomfortable leaving SSL off, we'd be happy to offer you a refund, but we'd definitely like to keep you onboard so we can get this solved.

No problem, keep me updated and I'll do whatever is needed to help get this resolved.

Link to post
Share on other sites
  • 4 weeks later...
On 5/25/2017 at 0:15 PM, Andrew Nelless said:

Hi @ga$E

Apologies regarding this. There are a few high priority issues blocking the v1.9 release. We're currently looking in the 2 week timeframe. Improved logging is definitely on the agenda short term, but I can't promise that we'll be able to reproduce or solve this SSL issue in v1.9.0

If you're uncomfortable leaving SSL off, we'd be happy to offer you a refund, but we'd definitely like to keep you onboard so we can get this solved.

Any update on this?

Link to post
Share on other sites
Paul Suarez
Hi @ga$E! I'm so sorry for the late reply on this thread. We have been so busy trying to reproduce the issue on our end. Unfortunately we, haven't been able to do so. I guess that might be due to different build versions of Windows from what you have and what we use.
 
I did experience lag/delay on my end. But I have fixed it by adding an exception on my third party firewall.
 
We understand that you have paid for it for you to make use of it. That being said, let me lay this card on the table again for you.
 
On 5/26/2017 at 0:15 AM, Andrew Nelless said:

If you're uncomfortable leaving SSL off, we'd be happy to offer you a refund,

Though, let me stress the next line again.

On 5/26/2017 at 0:15 AM, Andrew Nelless said:

but we'd definitely like to keep you onboard so we can get this solved.

If you can bear with us on this, please do. We'd love to get this bug (unconfirmed) fixed with your inputs. This should help everyone get back in using multiple computers seamlessly.;)

Link to post
Share on other sites
Paul Suarez
On 5/26/2017 at 10:10 PM, midakin said:

Nope both are enabled. It initially accepts then fails repeatedly after....

 

[2017-05-26T08:32:46] NOTE: started server, waiting for clients

[2017-05-26T08:32:46] INFO: watchdog status: ok

[2017-05-26T08:32:47] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-26T08:32:47] INFO: accepted secure socket

[2017-05-26T08:32:47] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD

[2017-05-26T08:32:47] NOTE: accepted client connection

[2017-05-26T08:32:48] NOTE: client "x-x" has connected

[2017-05-26T08:32:49] INFO: switch from "x-1" to "x-x" at 3519,689

[2017-05-26T08:32:49] INFO: leaving screen

[2017-05-26T08:32:49] INFO: screen "x-1" updated clipboard 0

1

[2017-05-26T08:33:02] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-26T08:33:02] ERROR: ssl error occurred (generic failure)

[2017-05-26T08:33:02] ERROR: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

[2017-05-26T08:33:02] ERROR: failed to accept secure socket

[2017-05-26T08:33:02] INFO: client connection may not be secure

[2017-05-26T08:33:18] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-05-26T08:33:18] ERROR: ssl error occurred (generic failure)

[2017-05-26T08:33:18] ERROR: error:140760FC:SSL routines:SSL23_GET_CLIENT_HELLO:unknown protocol

[2017-05-26T08:33:18] ERROR: failed to accept secure socket

[2017-05-26T08:33:18] INFO: client connection may not be secure

Hi @midakin. I have reproduced this by switching the SSL off on a client machine which is connected to a server with both SSL switched on. Same thing happens when I switched the SSL off on a server machine that has a client connected to it while their SSL are switched on.

You should stop Synergy on both machines first before toggling the SSL switch on their interface.

Link to post
Share on other sites
  • 4 months later...

I tried your suggestion and still ran into the same issue where it seems the SSL socket fails to connet

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

 

Log:

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:00] DEBUG2: no-op from

[2017-10-25T11:53:00] DEBUG2: onMouseMoveSecondary +71,+3

[2017-10-25T11:53:00] DEBUG2: move on DFW11-7210TMW to 3214,637

[2017-10-25T11:53:00] DEBUG2: send mouse move to "DFW11-7210TMW" 3214,637

[2017-10-25T11:53:00] DEBUG2: writef(DMMV%2i%2i)

[2017-10-25T11:53:00] DEBUG2: wrote 8 bytes

[2017-10-25T11:53:00] DEBUG2: writing secure socket:0000000003E989C0

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:00] DEBUG2: no-op from

[2017-10-25T11:53:00] DEBUG2: onMouseMoveSecondary +71,+0

[2017-10-25T11:53:00] DEBUG2: move on DFW11-7210TMW to 3285,637

[2017-10-25T11:53:00] DEBUG2: send mouse move to "DFW11-7210TMW" 3285,637

[2017-10-25T11:53:00] DEBUG2: writef(DMMV%2i%2i)

[2017-10-25T11:53:00] DEBUG2: wrote 8 bytes

[2017-10-25T11:53:00] DEBUG2: writing secure socket:0000000003E989C0

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:00] DEBUG2: no-op from

[2017-10-25T11:53:00] DEBUG2: onMouseMoveSecondary +76,+0

[2017-10-25T11:53:00] DEBUG2: find neighbor on right of "DFW11-7210TMW"

[2017-10-25T11:53:00] DEBUG2: "Midakin-PC" is on right of "DFW11-7210TMW" at 0.531250

[2017-10-25T11:53:00] DEBUG1: try to leave "DFW11-7210TMW" on right

[2017-10-25T11:53:00] INFO: switch from "DFW11-7210TMW" to "Midakin-PC" at 75,637

[2017-10-25T11:53:00] DEBUG1: send leave to "DFW11-7210TMW"

[2017-10-25T11:53:00] DEBUG2: writef(COUT)

[2017-10-25T11:53:00] DEBUG2: wrote 4 bytes

[2017-10-25T11:53:00] DEBUG2: writing secure socket:0000000003E989C0

[2017-10-25T11:53:00] INFO: entering screen

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: reading secure socket

[2017-10-25T11:53:00] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:01] DEBUG2: writef(CALV)

[2017-10-25T11:53:01] DEBUG2: wrote 4 bytes

[2017-10-25T11:53:01] DEBUG2: writing secure socket:0000000003E989C0

[2017-10-25T11:53:01] DEBUG2: reading secure socket

[2017-10-25T11:53:01] DEBUG2: reading secure socket

[2017-10-25T11:53:01] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CALV

[2017-10-25T11:53:01] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:01] DEBUG2: no-op from

[2017-10-25T11:53:06] DEBUG2: writef(CALV)

[2017-10-25T11:53:06] DEBUG2: wrote 4 bytes

[2017-10-25T11:53:06] DEBUG2: writing secure socket:0000000003E989C0

[2017-10-25T11:53:06] DEBUG2: reading secure socket

[2017-10-25T11:53:06] DEBUG2: reading secure socket

[2017-10-25T11:53:06] DEBUG2: want to read, error=2, attempt=1

[2017-10-25T11:53:06] DEBUG2: msg from "DFW11-7210TMW": CALV

[2017-10-25T11:53:06] DEBUG2: msg from "DFW11-7210TMW": CNOP

[2017-10-25T11:53:06] DEBUG2: no-op from

[2017-10-25T11:53:06] DEBUG2: dragging filename is cleared

[2017-10-25T11:53:06] DEBUG1: event: button press button=1

[2017-10-25T11:53:06] DEBUG1: onMouseDown id=1

[2017-10-25T11:53:07] DEBUG: stopping process

[2017-10-25T11:53:07] DEBUG1: event: button release button=1

[2017-10-25T11:53:07] DEBUG1: onMouseUp id=1

[2017-10-25T11:53:07] DEBUG: start ipc handle data

[2017-10-25T11:53:07] DEBUG: ipc read: ICMD

[2017-10-25T11:53:07] DEBUG2: readf(%s%1i)

[2017-10-25T11:53:07] DEBUG2: readf: read 0 byte string

[2017-10-25T11:53:07] DEBUG2: readf: read 1 byte integer: 0 (0x0)

[2017-10-25T11:53:07] DEBUG: finished ipc handle data

[2017-10-25T11:53:07] DEBUG: empty command, elevate=0

[2017-10-25T11:53:07] INFO: service command updated

[2017-10-25T11:53:07] INFO: process started but command is empty, shutting down

[2017-10-25T11:53:07] DEBUG2: writef(ISDN)

[2017-10-25T11:53:07] DEBUG2: wrote 4 bytes

[2017-10-25T11:53:07] DEBUG2: writef(ISDN)

[2017-10-25T11:53:07] DEBUG: ipc disconnect, closing stream

[2017-10-25T11:53:07] DEBUG2: wrote 4 bytes

[2017-10-25T11:53:07] DEBUG: ipc client write error

[2017-10-25T11:53:07] DEBUG: start ipc handle data

[2017-10-25T11:53:07] DEBUG: ipc read: ISDN

[2017-10-25T11:53:07] DEBUG: finished ipc handle data

[2017-10-25T11:53:07] DEBUG: ipc client proxy removed, connected=2

[2017-10-25T11:53:07] INFO: got ipc shutdown message

[2017-10-25T11:53:07] DEBUG1: stopping server

[2017-10-25T11:53:07] NOTE: disconnecting client "DFW11-7210TMW"

[2017-10-25T11:53:07] DEBUG1: send close "CBYE" to "DFW11-7210TMW"

[2017-10-25T11:53:07] DEBUG2: writef(CBYE)

[2017-10-25T11:53:07] DEBUG2: wrote 4 bytes

[2017-10-25T11:53:07] DEBUG2: writing secure socket:0000000003E989C0

[2017-10-25T11:53:07] DEBUG: active sides: 6

[2017-10-25T11:53:07] DEBUG: event queue is ready

[2017-10-25T11:53:08] DEBUG2: reading secure socket

[2017-10-25T11:53:08] DEBUG: ssl connection closed

[2017-10-25T11:53:08] NOTE: client "DFW11-7210TMW" has disconnected

[2017-10-25T11:53:09] DEBUG: unregistered hotkey id=1

[2017-10-25T11:53:09] DEBUG1: thread 0x00000838 exit

[2017-10-25T11:53:09] DEBUG1: stop listening for clients

[2017-10-25T11:53:17] WARNING: shutdown timed out after 10 secs, forcefully terminating

[2017-10-25T11:54:47] INFO: starting server

[2017-10-25T11:54:47] INFO: config file: C:/Users/Shawji/AppData/Local/Temp/qt_temp.wB9308

[2017-10-25T11:54:47] INFO: log level: INFO

[2017-10-25T11:54:47] DEBUG: start ipc handle data

[2017-10-25T11:54:47] DEBUG: ipc read: ICMD

[2017-10-25T11:54:47] DEBUG2: readf(%s%1i)

[2017-10-25T11:54:47] DEBUG2: readf: read 309 byte string

[2017-10-25T11:54:47] DEBUG2: readf: read 1 byte integer: 0 (0x0)

[2017-10-25T11:54:47] DEBUG: finished ipc handle data

[2017-10-25T11:54:47] DEBUG: new command, elevate=0 command="C:/Program Files/Synergy/synergys.exe" -f --no-tray --debug INFO --name Midakin-PC --ipc --stop-on-desk-switch --enable-drag-drop --enable-crypto --profile-dir "C:\Users\Shawji\AppData\Local" -c "C:/Users/Shawji/AppData/Local/Temp/qt_temp.Gg9308" --address :22 --serial-key 7B76313B70726F3B3B313B3B3B303B307D

[2017-10-25T11:54:47] INFO: service command updated

[2017-10-25T11:54:47] INFO: starting new process

[2017-10-25T11:54:47] INFO: activeDesktop:Default

[2017-10-25T11:54:47] INFO: starting new process

[2017-10-25T11:54:47] INFO: drag and drop enabled

[2017-10-25T11:54:47] NOTE: started server, waiting for clients

[2017-10-25T11:54:47] INFO: watchdog status: ok

[2017-10-25T11:54:47] INFO: OpenSSL 1.0.2 22 Jan 2015

[2017-10-25T11:54:48] INFO: accepted secure socket

[2017-10-25T11:54:48] INFO: AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD

[2017-10-25T11:54:48] NOTE: accepted client connection

[2017-10-25T11:54:48] NOTE: client "DFW11-7210TMW" has connected

[2017-10-25T11:54:50] INFO: switch from "Midakin-PC" to "DFW11-7210TMW" at 3285,354

[2017-10-25T11:54:50] INFO: leaving screen

[2017-10-25T11:54:50] INFO: screen "Midakin-PC" updated clipboard 0

[2017-10-25T11:54:50] INFO: screen "Midakin-PC" updated clipboard 1

[2017-10-25T11:54:50] INFO: switch from "DFW11-7210TMW" to "Midakin-PC" at 2,351

[2017-10-25T11:54:50] INFO: entering screen

[2017-10-25T11:54:50] INFO: switch from "Midakin-PC" to "DFW11-7210TMW" at 3285,353

[2017-10-25T11:54:50] INFO: leaving screen

[2017-10-25T11:56:42] INFO: switch from "DFW11-7210TMW" to "Midakin-PC" at 26,622

[2017-10-25T11:56:42] INFO: entering screen

[2017-10-25T11:59:01] INFO: switch from "Midakin-PC" to "DFW11-7210TMW" at 3285,612

[2017-10-25T11:59:01] INFO: leaving screen

[2017-10-25T11:59:01] INFO: screen "Midakin-PC" updated clipboard 0

[2017-10-25T11:59:01] INFO: screen "Midakin-PC" updated clipboard 1

[2017-10-25T11:59:02] INFO: switch from "DFW11-7210TMW" to "Midakin-PC" at 1,645

[2017-10-25T11:59:02] INFO: entering screen

Link to post
Share on other sites
  • 3 weeks later...

I've been running without SSL enabled with no issues....However would like to have SSL since now half my connection runs unencrypted.

FYI: My environment is work laptop to home computer, which goes through a VPN to Seattle and then back down to Dallas.

Network is not the issue.

Link to post
Share on other sites
FaithNoMore82

So I just saw this post while being here for another thread.

You all claim your networ is not the issue, without (mostly) not providing further details.

What if hardware is the issue?

Wouldn't posting your hardware specs help narrowing down this issue?

Just saying, don't hate me, maybe it wil help the devs.

Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
×
×
  • Create New...