github-starred/barrier

Fork 0

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

[GH-ISSUE #874] Issues with Linux Ubuntu x Windows 10 #696

New issue

Open

opened 2026-05-05 06:57:20 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

2026-05-05 06:57:20 -06:00

Owner

Originally created by @kevvrites on GitHub (Sep 14, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/874

I installed Barrier on my Windows 10 PC and on a Linux laptop running Ubuntu 20.04. I used snap to install on Linux, and I just downloaded the .exe file for Windows. I was able to launch Barrier on both applications.

My ISP gives each device a unique IP address, so the two devices are not able to "see" each other on the network. I used NordVPN to configure both devices to have the same IP address by connecting to the same server. However, when I attempt to run Barrier on both of them, nothing happens. The bottom left indicator reads "Barrier is running" on both Windows and Linux. I tried to have Windows as server, Linux as client, and nothing. I also tried Linux as server, Windows as client, and no response. I configured the server each time I swapped it. If the VPN was not on, then the client-side was stuck on "Barrier is starting...", which is why I believe the VPN is working. The displayed "IP address" under the server is not the one that the VPN lists, which is odd.

I've looked online for potential solutions but have not been able to find any. I'd really appreciate a solution or fix for this issue.

Originally created by @kevvrites on GitHub (Sep 14, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/874 I installed Barrier on my Windows 10 PC and on a Linux laptop running Ubuntu 20.04. I used snap to install on Linux, and I just downloaded the .exe file for Windows. I was able to launch Barrier on both applications. My ISP gives each device a unique IP address, so the two devices are not able to "see" each other on the network. I used NordVPN to configure both devices to have the same IP address by connecting to the same server. However, when I attempt to run Barrier on both of them, nothing happens. The bottom left indicator reads "Barrier is running" on both Windows and Linux. I tried to have Windows as server, Linux as client, and nothing. I also tried Linux as server, Windows as client, and no response. I configured the server each time I swapped it. If the VPN was not on, then the client-side was stuck on "Barrier is starting...", which is why I believe the VPN is working. The displayed "IP address" under the server is not the one that the VPN lists, which is odd. I've looked online for potential solutions but have not been able to find any. I'd really appreciate a solution or fix for this issue.

gitea-mirror commented

2026-05-05 06:57:23 -06:00

Author

Owner

@aoztaskin commented on GitHub (Sep 15, 2020):

Are they connected to different routers? Assuming not, you should look into https://en.wikipedia.org/wiki/Private_network or an introductory networking tutorial. Basically these devices are in the same local network and should be able to connect to each other using their local IP addresses. What you get from the ISP and the VPN does not matter as long as they are in the same private network.

Try creating a server on a computer and entering its IP address as the "Server IP" in the other. Watch the logs and configure the server with the correct computer name. You should also try this from the project's wiki https://github.com/debauchee/barrier/wiki/Troubleshooting#server-reachability-ping

@aoztaskin commented on GitHub (Sep 15, 2020): Are they connected to different routers? Assuming not, you should look into https://en.wikipedia.org/wiki/Private_network or an introductory networking tutorial. Basically these devices are in the same local network and should be able to connect to each other using their local IP addresses. What you get from the ISP and the VPN does not matter as long as they are in the same private network. Try creating a server on a computer and entering its IP address as the "Server IP" in the other. Watch the logs and configure the server with the correct computer name. You should also try this from the project's wiki https://github.com/debauchee/barrier/wiki/Troubleshooting#server-reachability-ping

gitea-mirror commented

2026-05-05 06:57:25 -06:00

Author

Owner

@kevvrites commented on GitHub (Sep 15, 2020):

Are they connected to different routers?
It's hard to tell, since I am based in an apartment and the wireless connection is through the ISP. My PC and the laptop are sharing the same IP address, so they should be on the same local network. I am not sure how to set up my own server on the PC as I don't have direct access to the router. I attempted to connect by manually filling the "Server IP" but I ran into the same issues (either labeled "connected" with no functionality, or labeled "barrier is starting").

I am still quite new to Ubuntu and my knowledge of device connectivity is limited. I was hoping that Barrier would "just work" as I saw via videos and in the Wiki. I am not sure where the issues are originating, but it feels like I need to learn a ton of information just to get a chance to fix it.

@kevvrites commented on GitHub (Sep 15, 2020): > Are they connected to different routers? It's hard to tell, since I am based in an apartment and the wireless connection is through the ISP. My PC and the laptop are sharing the same IP address, so they should be on the same local network. I am not sure how to set up my own server on the PC as I don't have direct access to the router. I attempted to connect by manually filling the "Server IP" but I ran into the same issues (either labeled "connected" with no functionality, or labeled "barrier is starting"). I am still quite new to Ubuntu and my knowledge of device connectivity is limited. I was hoping that Barrier would "just work" as I saw via videos and in the Wiki. I am not sure where the issues are originating, but it feels like I need to learn a ton of information just to get a chance to fix it.

gitea-mirror commented

2026-05-05 06:57:28 -06:00

Author

Owner

@shymega commented on GitHub (Sep 15, 2020):

There's still configuration involved, and its not a ton of information you need to know... nothing 'just works' to be honest. We use Zeroconf to discover other devices, but its not always working, so yes, manual config is sometimes needed.

Unless your devices are isolated in VLANs/subnets, there is no reason why they cannot "see" each other.

@shymega commented on GitHub (Sep 15, 2020): There's still configuration involved, and its not a ton of information you need to know... nothing 'just works' to be honest. We use Zeroconf to discover other devices, but its not always working, so yes, manual config is sometimes needed. Unless your devices are isolated in VLANs/subnets, there is _no reason_ why they cannot "see" each other.

gitea-mirror commented

2026-05-05 06:57:30 -06:00

Author

Owner

@codisfy commented on GitHub (Sep 17, 2020):

@kevvrites See using the "show log " option what does it show? It can help you.
For me I also thought it would "just work" although it does indeed, but I had to go into the server configuration(use configure server button) and added a screen and matched the screen name of the client(double tap on added screen to configure).
I don't know if this is needed but it worked for me

@codisfy commented on GitHub (Sep 17, 2020): @kevvrites See using the "show log " option what does it show? It can help you. For me I also thought it would "just work" although it does indeed, but I had to go into the server configuration(use configure server button) and added a screen and matched the screen name of the client(double tap on added screen to configure). I don't know if this is needed but it worked for me

gitea-mirror commented

2026-05-05 06:57:32 -06:00

Author

Owner

@kevvrites commented on GitHub (Sep 17, 2020):

The show log option does not state any additional issues, as it displays the same message I have found on other people's cases. I did use the server configuration to create two screens when I attempted to connect the computers. @shymega I am not familiar with the process of connections, but there are a lot of points of failure and things to check (Firewall, SSL, IPv4, IPv6) and I am not familiar with troubleshooting each one. I have found guides and cleared the issues with firewall, but there is no additional information displayed either from the system log or from my command line to give me any idea of where the issue is. I can't tell if my devices are somehow isolated on separate private networks, or if there's a security feature that doesn't allow information to pass through port 24800, or any other issues. Online solutions for common problems have not led me to a functional system, so I have stopped trying for now. I need to learn a lot more about the actual process and underlying technology before I can even understand what's happening.

@kevvrites commented on GitHub (Sep 17, 2020): The show log option does not state any additional issues, as it displays the same message I have found on other people's cases. I did use the server configuration to create two screens when I attempted to connect the computers. @shymega I am not familiar with the process of connections, but there are a lot of points of failure and things to check (Firewall, SSL, IPv4, IPv6) and I am not familiar with troubleshooting each one. I have found guides and cleared the issues with firewall, but there is no additional information displayed either from the system log or from my command line to give me any idea of where the issue is. I can't tell if my devices are somehow isolated on separate private networks, or if there's a security feature that doesn't allow information to pass through port 24800, or any other issues. Online solutions for common problems have not led me to a functional system, so I have stopped trying for now. I need to learn a lot more about the actual process and underlying technology before I can even understand what's happening.

gitea-mirror commented

2026-05-05 06:57:33 -06:00

Author

Owner

@maxgolov commented on GitHub (Oct 3, 2020):

@kevvrites - please check if you have the Scroll Lock enabled on Windows machine. I just ended-up debugging Win 10 vs. Kubuntu 20.04, only to realize that I accidentally had the Scroll Lock pressed on my Windows machine! 😀 Toggle your debug verbosity to maximum on Windows (Debug2), check if you possibly have something like this in the log?

[2020-10-03T02:07:27] DEBUG2: "NUC7i5BNH" is on right of "MaxOMEN" at 0.251620
[2020-10-03T02:07:27] DEBUG1: try to leave "MaxOMEN" on right
[2020-10-03T02:07:27] DEBUG1: locked to screen

The fix is to toggle the Scroll Lock key.

The other thing to check is if you have SSL enabled on both ends. If you don't have [x] Enable SSL checked on server, but enabled on the client, then Linux-side (Ubuntu 20.04) is gonna fail with ssl3_get_record wrong version number.

Everything works well for me (Windows 10 x Ubuntu 20.04, compiled from latest master) on two computers in two separate isolated subnets with routing between the two. I have to manually specify the server IP (auto-discovery across the two subnets does not work), then everything works great!

@maxgolov commented on GitHub (Oct 3, 2020): @kevvrites - please check if you have the Scroll Lock enabled on Windows machine. I just ended-up debugging Win 10 vs. Kubuntu 20.04, only to realize that I accidentally had the Scroll Lock pressed on my Windows machine! 😀 Toggle your debug verbosity to maximum on Windows (Debug2), check if you possibly have something like this in the log? ```console [2020-10-03T02:07:27] DEBUG2: "NUC7i5BNH" is on right of "MaxOMEN" at 0.251620 [2020-10-03T02:07:27] DEBUG1: try to leave "MaxOMEN" on right [2020-10-03T02:07:27] DEBUG1: locked to screen ``` The fix is to toggle the Scroll Lock key. The other thing to check is if you have SSL enabled on both ends. If you don't have `[x] Enable SSL` checked on server, but enabled on the client, then Linux-side (Ubuntu 20.04) is gonna fail with `ssl3_get_record wrong version number`. Everything works well for me (Windows 10 x Ubuntu 20.04, compiled from latest `master`) on two computers in two separate isolated subnets with routing between the two. I have to manually specify the server IP (auto-discovery across the two subnets does not work), then everything works great!

No labels

Rows
Columns