Server: Windows 10
Client: MacOS 10.15.2
2.3.2-Release-210c2b70
Cannot use Barrier at all. Checked in multiple IP environments (both work and home): same issue.
[2020-01-21T09:53:44] INFO: starting client
[2020-01-21T09:53:44] INFO: config file: /private/var/folders/ky/pq0rhqf557bgrk57p59rgpww0000gn/T/Barrier.uFVfif
[2020-01-21T09:53:44] INFO: log level: INFO
[2020-01-21T09:53:44] INFO: drag and drop enabled
[2020-01-21T09:53:44] NOTE: started client
[2020-01-21T09:53:44] NOTE: connecting to '10.4.15.67': 10.4.15.67:24800
[2020-01-21T09:53:44] INFO: OpenSSL 1.0.2t 10 Sep 2019
2020-01-21 09:53:44.452 barrierc[1544:60127] starting cocoa loop
[2020-01-21T09:53:59] WARNING: failed to connect to server: Timed out
[2020-01-21T09:54:00] NOTE: connecting to '10.4.15.67': 10.4.15.67:24800
[2020-01-21T09:54:00] INFO: OpenSSL 1.0.2t 10 Sep 2019
[2020-01-21T09:54:15] WARNING: failed to connect to server: Timed out
[2020-01-21T09:54:16] NOTE: connecting to '10.4.15.67': 10.4.15.67:24800
[2020-01-21T09:54:16] INFO: OpenSSL 1.0.2t 10 Sep 2019
[2020-01-21T09:54:23] INFO: stopping barrier desktop process
[2020-01-21T09:54:28] ERROR: process exited with error code: 9
Same issue here, but server is on 10.14.6 and client is ubuntu 19.04
same problem,it seems we have met a same bug.
I'm having the same issue on Windows 10 and Arch. I'll note that initially I thought this may have been due to SSL howerver after disabling SSL I'm still getting "Barrier is starting." on both client and server.
@goldmahn In the log posted you have timeouts:
[2020-01-21T09:53:59] WARNING: failed to connect to server: Timed out
That means it's not able to connect to the server. If you can ping the server the incoming connection might be getting blocked. You can rule out the barrier client if you can connect with openssl:
openssl s_client -connect hostname:24800
If openssl is able to connect, it is a problem with the barrier client. If you still get a timeout with openssl then there is either a network issue, DNS issue (if using a hostname), or the operating system is blocking that port (i.e. with a firewall).
This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.