github-starred/barrier

Fork 0

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

[GH-ISSUE #1973] Error “Failed to connect to server: timed out” ; #1443

New issue

Closed

opened 2026-05-05 07:50:43 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:50:43 -06:00

Owner

Originally created by @0thigs on GitHub (Sep 7, 2023).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1973

What happened?

When I try to set up Barrier to share my keyboard and mouse between my Windows 10 server and my Ubuntu 22.04 Linux client, I encounter the error "Failed to connect to server: timed out."

This indicates that communication between my client and the Barrier server is not successfully established within a specific time frame.

Additional Information:

-My Windows 10 server is using an Internet connection via USB tethering from my mobile device.
-Both my devices (server and client) are on the same local network.
-My Barrier client is configured to connect to the Barrier server using both the server's name and its IP address.

I have already tried:

-Disabling SSL on both ends
-Attempted to create a separate configuration file
-Allowed Barrier through the Windows firewall, and even tried disabling the firewall altogether.

Unfortunately, none of these steps have resolved the issue.

LOGS:

NOTE: started client
NOTE: connecting to '192.168.XX.XXX': '192.168.XX.XXX:24800
WARNING: failed to connect to server: Timed out

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

No response

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

Linux, Windows

What OS versions are you using?

Ubuntu 22.04 as Client
Windows 10 as Server

Relevant log output

NOTE: started client
NOTE: connecting to '192.168.xx.xxx': '192.168.xx.xxx:24800
WARNING: failed to connect to server: Timed out

Any other information

No response

Originally created by @0thigs on GitHub (Sep 7, 2023). Original GitHub issue: https://github.com/debauchee/barrier/issues/1973 ### What happened? When I try to set up Barrier to share my keyboard and mouse between my Windows 10 server and my Ubuntu 22.04 Linux client, I encounter the error **"Failed to connect to server: timed out."** This indicates that communication between my client and the Barrier server is not successfully established within a specific time frame. Additional Information: -My Windows 10 server is using an Internet connection via USB tethering from my mobile device. -Both my devices (server and client) are on the same local network. -My Barrier client is configured to connect to the Barrier server using both the server's name and its IP address. I have already tried: -Disabling SSL on both ends -Attempted to create a separate configuration file -Allowed Barrier through the Windows firewall, and even tried disabling the firewall altogether. Unfortunately, none of these steps have resolved the issue. LOGS: NOTE: started client NOTE: connecting to '192.168.XX.XXX': '192.168.XX.XXX:24800 WARNING: failed to connect to server: Timed out ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? _No response_ ### What OSes are you seeing the problem on? (Check all that apply) Linux, Windows ### What OS versions are you using? Ubuntu 22.04 as Client Windows 10 as Server ### Relevant log output ```shell NOTE: started client NOTE: connecting to '192.168.xx.xxx': '192.168.xx.xxx:24800 WARNING: failed to connect to server: Timed out ``` ### Any other information _No response_

gitea-mirror closed this issue

2026-05-05 07:50:44 -06:00

gitea-mirror commented

2026-05-05 07:50:46 -06:00

Author

Owner

@ETLang commented on GitHub (Sep 11, 2023):

+1 to this. Barrier was working fine for me all last week. and for some reason today I'm getting this problem. I am not using SSL. My Ubuntu machine and my Windows machine are on the same LAN. I am using default settings for almost everything. I made sure no duplicate processes were lurking in the background. I pinged each machine from the other successfully. I stopped/started both client and server in every sequence possible. Still, I get this same error.

@ETLang commented on GitHub (Sep 11, 2023): +1 to this. Barrier was working fine for me all last week. and for some reason today I'm getting this problem. I am not using SSL. My Ubuntu machine and my Windows machine are on the same LAN. I am using default settings for almost everything. I made sure no duplicate processes were lurking in the background. I pinged each machine from the other successfully. I stopped/started both client and server in every sequence possible. Still, I get this same error.

gitea-mirror commented

2026-05-05 07:50:47 -06:00

Author

Owner

@0thigs commented on GitHub (Sep 12, 2023):

Bro, I solved my problem. It was because of the USB Tethering.

Probably the problem was IP I was getting from the USB Tethering, but now I am using a LAN cable and it works.

@0thigs commented on GitHub (Sep 12, 2023): Bro, I solved my problem. It was because of the USB Tethering. Probably the problem was IP I was getting from the USB Tethering, but now I am using a LAN cable and it works.

gitea-mirror commented

2026-05-05 07:50:48 -06:00

Author

Owner

@0thigs commented on GitHub (Sep 12, 2023):

+1 to this. Barrier was working fine for me all last week. and for some reason today I'm getting this problem. I am not using SSL. My Ubuntu machine and my Windows machine are on the same LAN. I am using default settings for almost everything. I made sure no duplicate processes were lurking in the background. I pinged each machine from the other successfully. I stopped/started both client and server in every sequence possible. Still, I get this same error.

What are you getting in your LOG?

@0thigs commented on GitHub (Sep 12, 2023): > +1 to this. Barrier was working fine for me all last week. and for some reason today I'm getting this problem. I am not using SSL. My Ubuntu machine and my Windows machine are on the same LAN. I am using default settings for almost everything. I made sure no duplicate processes were lurking in the background. I pinged each machine from the other successfully. I stopped/started both client and server in every sequence possible. Still, I get this same error. What are you getting in your LOG?

gitea-mirror commented

2026-05-05 07:50:51 -06:00

Author

Owner

@ETLang commented on GitHub (Sep 12, 2023):

This morning Barrier decided to work again. I haven't even rebooted. XD Anyway, next time it misbehaves I'll capture the log at the moment, but to answer your question as best I can, it looked identical to the OP's log.

@ETLang commented on GitHub (Sep 12, 2023): > This morning Barrier decided to work again. I haven't even rebooted. XD Anyway, next time it misbehaves I'll capture the log at the moment, but to answer your question as best I can, it looked identical to the OP's log.

gitea-mirror commented

2026-05-05 07:50:52 -06:00

Author

Owner

@jonathan-analist commented on GitHub (Mar 24, 2024):

Aparentemente esse erro acontece somente na rede Wifi

@jonathan-analist commented on GitHub (Mar 24, 2024): Aparentemente esse erro acontece somente na rede Wifi