github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #1775] SSL Error and Connection Timeout on Client Start Process #1306

New issue

Open

opened 2026-05-05 07:42:54 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 07:42:54 -06:00

Owner

Originally created by @EPacifist on GitHub (Sep 9, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1775

What happened?

I have followed the "Always getting Timeout while connecting" resolved issue but to no avail. Here are the logs:
[2022-09-09T15:34:15] INFO: starting client [2022-09-09T15:34:15] INFO: config file: /tmp/Barrier.nS1476 [2022-09-09T15:34:15] INFO: log level: INFO [2022-09-09T15:34:15] INFO: zeroconf server detected: 10.2.18.185 [2022-09-09T15:34:15] INFO: zeroconf server detected: 10.2.18.235 [2022-09-09T15:34:15] NOTE: started client [2022-09-09T15:34:15] NOTE: connecting to '10.2.18.185': 10.2.18.185:24800 [2022-09-09T15:34:15] INFO: OpenSSL 1.1.1 11 Sep 2018 [2022-09-09T15:34:15] ERROR: ssl error occurred (system call failure) [2022-09-09T15:34:15] ERROR: Broken pipe [2022-09-09T15:34:15] ERROR: failed to connect secure socket [2022-09-09T15:34:30] WARNING: failed to connect to server: Timed out [2022-09-09T15:34:31] NOTE: connecting to '10.2.18.185': 10.2.18.185:24800 [2022-09-09T15:34:31] INFO: OpenSSL 1.1.1 11 Sep 2018 [2022-09-09T15:34:31] ERROR: ssl error occurred (system call failure) [2022-09-09T15:34:31] ERROR: failed to connect secure socket [2022-09-09T15:34:46] WARNING: failed to connect to server: Timed out [2022-09-09T15:34:47] NOTE: connecting to '10.2.18.185': 10.2.18.185:24800 [2022-09-09T15:34:47] INFO: OpenSSL 1.1.1 11 Sep 2018 [2022-09-09T15:34:47] ERROR: ssl error occurred (system call failure) [2022-09-09T15:34:47] ERROR: failed to connect secure socket

I have opened the firewall, verified the port is open through powershell and have connected successfully through the Ubuntu client through nc:

gordo@gordo-tegra-l4t:~$ nc -vz 10.2.18.185 24800 Connection to 10.2.18.185 24800 port [tcp/*] succeeded!

Yet it refuses to connect due to an SSL error.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

cobalt2727/L4T-Megascript

What OSes are you seeing the problem on? (Check all that apply)

Linux, Windows

What OS versions are you using?

Windows server, Ubuntu 18.04 L4T

Relevant log output

No response

Any other information

No response

Originally created by @EPacifist on GitHub (Sep 9, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1775 ### What happened? I have followed the "Always getting Timeout while connecting" resolved issue but to no avail. Here are the logs: `[2022-09-09T15:34:15] INFO: starting client [2022-09-09T15:34:15] INFO: config file: /tmp/Barrier.nS1476 [2022-09-09T15:34:15] INFO: log level: INFO [2022-09-09T15:34:15] INFO: zeroconf server detected: 10.2.18.185 [2022-09-09T15:34:15] INFO: zeroconf server detected: 10.2.18.235 [2022-09-09T15:34:15] NOTE: started client [2022-09-09T15:34:15] NOTE: connecting to '10.2.18.185': 10.2.18.185:24800 [2022-09-09T15:34:15] INFO: OpenSSL 1.1.1 11 Sep 2018 [2022-09-09T15:34:15] ERROR: ssl error occurred (system call failure) [2022-09-09T15:34:15] ERROR: Broken pipe [2022-09-09T15:34:15] ERROR: failed to connect secure socket [2022-09-09T15:34:30] WARNING: failed to connect to server: Timed out [2022-09-09T15:34:31] NOTE: connecting to '10.2.18.185': 10.2.18.185:24800 [2022-09-09T15:34:31] INFO: OpenSSL 1.1.1 11 Sep 2018 [2022-09-09T15:34:31] ERROR: ssl error occurred (system call failure) [2022-09-09T15:34:31] ERROR: failed to connect secure socket [2022-09-09T15:34:46] WARNING: failed to connect to server: Timed out [2022-09-09T15:34:47] NOTE: connecting to '10.2.18.185': 10.2.18.185:24800 [2022-09-09T15:34:47] INFO: OpenSSL 1.1.1 11 Sep 2018 [2022-09-09T15:34:47] ERROR: ssl error occurred (system call failure) [2022-09-09T15:34:47] ERROR: failed to connect secure socket` I have opened the firewall, verified the port is open through powershell and have connected successfully through the Ubuntu client through nc: `gordo@gordo-tegra-l4t:~$ nc -vz 10.2.18.185 24800 Connection to 10.2.18.185 24800 port [tcp/*] succeeded!` Yet it refuses to connect due to an SSL error. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? cobalt2727/L4T-Megascript ### What OSes are you seeing the problem on? (Check all that apply) Linux, Windows ### What OS versions are you using? Windows server, Ubuntu 18.04 L4T ### Relevant log output _No response_ ### Any other information _No response_

gitea-mirror commented

2026-05-05 07:42:56 -06:00

Author

Owner

@EPacifist commented on GitHub (Sep 9, 2022):

Testnet powershell output:



ComputerName            : 10.2.18.185
RemoteAddress           : 10.2.18.185
RemotePort              : 24800
NameResolutionResults   : 10.2.18.185
                          LAPTOP-ZG152021.veracitynetworks.net
MatchingIPsecRules      :
NetworkIsolationContext : Private Network
IsAdmin                 : False
InterfaceAlias          : Ethernet 2
SourceAddress           : 10.2.18.185
NetRoute (NextHop)      : 0.0.0.0
TcpTestSucceeded        : True```

@EPacifist commented on GitHub (Sep 9, 2022): Testnet powershell output: ```PS C:\Users\gordo> Test-NetConnection -Port 24800 -ComputerName 10.2.18.185 -InformationLevel Detailed ComputerName : 10.2.18.185 RemoteAddress : 10.2.18.185 RemotePort : 24800 NameResolutionResults : 10.2.18.185 LAPTOP-ZG152021.veracitynetworks.net MatchingIPsecRules : NetworkIsolationContext : Private Network IsAdmin : False InterfaceAlias : Ethernet 2 SourceAddress : 10.2.18.185 NetRoute (NextHop) : 0.0.0.0 TcpTestSucceeded : True```

gitea-mirror commented

2026-05-05 07:42:58 -06:00

Author

Owner

@mahmoudbahaa commented on GitHub (Sep 19, 2022):

Go to the Barrier -> change settings of each of the server and the client(s) and de-select enable ssl option and reload on server and then on clients

@mahmoudbahaa commented on GitHub (Sep 19, 2022): Go to the **Barrier -> change settings** of each of the server and the client(s) and de-select **enable ssl** option and reload on server and then on clients

No labels

Rows
Columns