You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue has been migrated from old Barrier Github repository debauchee/barrier#480
Issue created on: 2019-10-28 by @Ryan-Te
Issue last updated on: 2021-08-28
So i installed it on both my windows 7 and ubuntu machines. i set up a server on the win pc but when i try to connect on my linux pc it gets stuck at "Barrier Is starting". i have ubuntu 18.04.3 LTS
Here Is the log:
Qt: Session management error: None of the authentication protocols specified are supported
("-f", "--no-tray", "--debug", "INFO", "--name", "Ryan-Ubuntu", "--enable-crypto", "[192.168.0.135]:24800")
("-f", "--no-tray", "--debug", "INFO", "--name", "Ryan-Ubuntu", "--enable-crypto", "[192.168.0.135]:24800")
("-f", "--no-tray", "--debug", "INFO", "--name", "Ryan-Ubuntu", "--enable-crypto", "[192.168.0.135]:24800")
("-f", "--no-tray", "--debug", "INFO", "--name", "Ryan-Ubuntu", "--enable-crypto", "[192.168.0.152]:24800")
I had similar issue, but I did not look at the log to see what it said.
How I resolved it, is on the server machine select configure server and delete all machines that are in "Screens and links". Once I did that and reloaded barrier on both machines it was working. Hope this helps.
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
Having the same issue and this one worked for me, thanks
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
Awesome man, it worked for me too. I was stuck from last hour or so. Thanks a ton.... :)
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
[SOLVED ]same here, added a screen on server config with the name of the client computer, reloaded, but client is stuck on "Barrier is starting".
Server is connected to network via RJ45 cable, but Client via WIFI. Both to same router
[SOLVED ]same here, added a screen on server config with the name of the client computer, reloaded, but client is stuck on "Barrier is starting".
Server is connected to network via RJ45 cable, but Client via WIFI. Both to same router
SOLVED DISABLING FIREWALL
[SOLVED] [ EXTRA SOLUTION]
I had the same setup and disabling windows firewall worked but to keep windows firewall running i added an Inbound rule to the 24800 port (the one that barrier is using) in Windows defender firewall with advanced security after that barrier started to work again with firewall enabled again.
I cant seem to make it work from Windows 10 (server) to arch (client). I Tried doing what @minhmoc says, I tried disabling firewall completely and ssl but still no results. I keep getting 'Barrier is starting' on arch!
I know there's got something to do with Windows cause I tried it from two arch machines and it worked flawlessly!
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
In my case, because I've tried multiple times starting and closing Barrier on the Windows machine as the server, the application doesn't actually exist. So make sure there is not an existing barrier process running in task manager. Then start barrier again which should be able to run.
When you're installing barrier as a snap, don't install it via a UI! Install it via the terminal like so:
snap install --devmode barrier
This will circumvent all security sandboxing snap normally applies to an install, which prevents barrier from accessing the network socket properly. I'm sure there's a way to fix this when building the snap package, but as a workaround, this was good enough for me.
When you're installing barrier as a snap, don't install it via a UI! Install it via the terminal like so:
snap install --devmode barrier
This will circumvent all security sandboxing snap normally applies to an install, which prevents barrier from accessing the network socket properly. I'm sure there's a way to fix this when building the snap package, but as a workaround, this was good enough for me.
Installing the snap with --devmode is dangerous and defeats the whole idea behind snaps security; it should only be done for debugging and diagnosing issues. I use this snap daily with no issues myself, fwiw. Here's a complete guide to debugging issues with snaps. Also, check that the network interface/permission is connected/granted, via snap connections barrier.
@maxiberta It didn't really matter in my case, this was on a temporary machine with no important data, but you're right, it's not the right way. I tried uninstalling and reinstalling again, and I did check the permissions as you suggested, and this time it worked out of the box without any fiddling. Very strange, not sure what caused it to break the first time around.
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
I had the same issues. After an hour of searching Internet I got it working.
My server is Windows 10 and Client is MacOS Catalina.
Barrier was picking up the wrong IP Address which was my Ethernet IP Address.
So make sure you run ipconfig on the server, in my case it's Windows 10
and see the correct IP Address Under Wireless LAN adapter Wi-Fi IPV4 address.
Make sure you give the same Screen Name
In my case the name is mac (Windows 10 Screenshot)
Mac OS Screenshot
I had problems if my Wifi is set to password protected (which is just my mobile hotspot). So to get around that I made it public and limited the connections to it.
Had the same problem, the issue was that both computers had the almost exact same screen name (one being Title Cased, the other not), fixed by using different screen names.
When you're installing barrier as a snap, don't install it via a UI! Install it via the terminal like so: snap install --devmode barrier
This will circumvent all security sandboxing snap normally applies to an install, which prevents barrier from accessing the network socket properly. I'm sure there's a way to fix this when building the snap package, but as a workaround, this was good enough for me.
Installing the snap with --devmode is dangerous and defeats the whole idea behind snaps security; it should only be done for debugging and diagnosing issues. I use this snap daily with no issues myself, fwiw. Here's a complete guide to debugging issues with snaps. Also, check that the network interface/permission is connected/granted, via snap connections barrier.
could you please explain how we can fix this without the devmode?
I cannot understand where to look for this network socket security issue in snap
In my case, for some reason Windows disabled Network Discovery. I realized this because I couldn't share files over my LAN.
In Windows I went to the Network folder and I was prompted if I wanted to enable network discovery and file sharing for my (private) network and everything got fixed.
Another cause of this issue is having a registered keystroke that points to a screen that does not exist, in my case i had a switch to screen to one i deleted.
ghost
closed this as
So i installed it on both my windows 7 and ubuntu machines. i set up a server on the win pc but when i try to connect on my linux pc it gets stuck at "Barrier Is starting". i have ubuntu 18.04.3 LTS
Here Is the log:
Qt: Session management error: None of the authentication protocols specified are supported
("-f", "--no-tray", "--debug", "INFO", "--name", "Ryan-Ubuntu", "--enable-crypto", "[192.168.0.135]:24800")
("-f", "--no-tray", "--debug", "INFO", "--name", "Ryan-Ubuntu", "--enable-crypto", "[192.168.0.135]:24800")
("-f", "--no-tray", "--debug", "INFO", "--name", "Ryan-Ubuntu", "--enable-crypto", "[192.168.0.135]:24800")
("-f", "--no-tray", "--debug", "INFO", "--name", "Ryan-Ubuntu", "--enable-crypto", "[192.168.0.152]:24800")
I had similar issue, but I did not look at the log to see what it said.
How I resolved it, is on the server machine select configure server and delete all machines that are in "Screens and links". Once I did that and reloaded barrier on both machines it was working. Hope this helps.
I just recently have the same issue.
I make it work just by adding new computer on the Configure Server, and name that computer with the same name appeared in client machine (for example in your case the name should be set to Ryan-Ubuntu). Then reload and it works perfectly.
Hope this help.
Having the same issue and this one worked for me, thanks
I Tried This And It Worked! Thanks
Awesome man, it worked for me too. I was stuck from last hour or so. Thanks a ton.... :)
Worked here as well, cheers!
Amazing ! (Win10 as server, Ubuntu16 as client)
I got the same problem. and after I drag the icon to add a new computer, it wouldn't work, too.
But, when I closed the SSL, it works.
[SOLVED ]same here, added a screen on server config with the name of the client computer, reloaded, but client is stuck on "Barrier is starting".
Server is connected to network via RJ45 cable, but Client via WIFI. Both to same router
SOLVED DISABLING FIREWALL
Disabling SSL fixed it for me as well.
[SOLVED] [ EXTRA SOLUTION]
I had the same setup and disabling windows firewall worked but to keep windows firewall running i added an Inbound rule to the 24800 port (the one that barrier is using) in Windows defender firewall with advanced security after that barrier started to work again with firewall enabled again.
Hello! Tried everything: Disabling SSL, Disabling Firewall and nothing... What can I do?
I cant seem to make it work from Windows 10 (server) to arch (client). I Tried doing what @minhmoc says, I tried disabling firewall completely and ssl but still no results. I keep getting 'Barrier is starting' on arch!
I know there's got something to do with Windows cause I tried it from two arch machines and it worked flawlessly!
Tried everything too and still have this problem with macOS (Server) and Windows 10 (Client)
In my opinion that should be on FAQ.
yes this one and one solution by @minhmoc worked for me.
In my case, because I've tried multiple times starting and closing Barrier on the Windows machine as the server, the application doesn't actually exist. So make sure there is not an existing barrier process running in task manager. Then start barrier again which should be able to run.
When you're installing barrier as a snap, don't install it via a UI! Install it via the terminal like so:
snap install --devmode barrierThis will circumvent all security sandboxing snap normally applies to an install, which prevents barrier from accessing the network socket properly. I'm sure there's a way to fix this when building the snap package, but as a workaround, this was good enough for me.
Installing the snap with
--devmodeis dangerous and defeats the whole idea behind snaps security; it should only be done for debugging and diagnosing issues. I use this snap daily with no issues myself, fwiw. Here's a complete guide to debugging issues with snaps. Also, check that thenetworkinterface/permission is connected/granted, viasnap connections barrier.@maxiberta It didn't really matter in my case, this was on a temporary machine with no important data, but you're right, it's not the right way. I tried uninstalling and reinstalling again, and I did check the permissions as you suggested, and this time it worked out of the box without any fiddling. Very strange, not sure what caused it to break the first time around.
Tried this and it works like a charm.
Thank You
I had the same issues. After an hour of searching Internet I got it working.
My server is Windows 10 and Client is MacOS Catalina.
Barrier was picking up the wrong IP Address which was my Ethernet IP Address.
So make sure you run
ipconfigon the server, in my case it's Windows 10and see the correct IP Address Under Wireless LAN adapter Wi-Fi IPV4 address.
Make sure you give the same Screen Name
In my case the name is mac (Windows 10 Screenshot)
Mac OS Screenshot
I had problems if my Wifi is set to password protected (which is just my mobile hotspot). So to get around that I made it public and limited the connections to it.
That's it. I hope it helps somebody :)
Had the same problem, the issue was that both computers had the almost exact same screen name (one being Title Cased, the other not), fixed by using different screen names.
could you please explain how we can fix this without the devmode?
I cannot understand where to look for this network socket security issue in snap
okay, I got it working by disabling "auto-config" and using the other ip address from the server barrier in "server ip".
In my case, for some reason Windows disabled Network Discovery. I realized this because I couldn't share files over my LAN.
In Windows I went to the Network folder and I was prompted if I wanted to enable network discovery and file sharing for my (private) network and everything got fixed.
Another cause of this issue is having a registered keystroke that points to a screen that does not exist, in my case i had a switch to screen to one i deleted.
How to disable/close SSL?
The text was updated successfully, but these errors were encountered: