[GH-ISSUE #1421] Barrier is not working #1097

Open
opened 2026-05-05 07:28:27 -06:00 by gitea-mirror · 40 comments
Owner

Originally created by @geekypathak21 on GitHub (Nov 11, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1421

What happened?

Client is always saying "Barrier is starting" but it does not connect. It am stuck with this situation. I also checked my server configuration nothing is wrong with that.

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Installed from snap.

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

Linux

What OS versions are you using?

I am using Ubuntu 21.10 as a server and Ubuntu 20.10 as client.

Relevant log output

No response

Any other information

No response

Originally created by @geekypathak21 on GitHub (Nov 11, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1421 ### What happened? Client is always saying "Barrier is starting" but it does not connect. It am stuck with this situation. I also checked my server configuration nothing is wrong with that. ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? Installed from snap. ### What OSes are you seeing the problem on? (Check all that apply) Linux ### What OS versions are you using? I am using Ubuntu 21.10 as a server and Ubuntu 20.10 as client. ### Relevant log output _No response_ ### Any other information _No response_
Author
Owner

@brokeblackjew commented on GitHub (Nov 12, 2021):

I am using ubuntu and having the same problem. My server is a windows machine.

<!-- gh-comment-id:966888839 --> @brokeblackjew commented on GitHub (Nov 12, 2021): I am using ubuntu and having the same problem. My server is a windows machine.
Author
Owner

@dnet890 commented on GitHub (Nov 12, 2021):

Windows 10 also and it says barrier is running. But, nothing happens

<!-- gh-comment-id:967035199 --> @dnet890 commented on GitHub (Nov 12, 2021): Windows 10 also and it says barrier is running. But, nothing happens
Author
Owner

@TunaLobster commented on GitHub (Nov 13, 2021):

For each of you, are server and client the same version?

<!-- gh-comment-id:968098664 --> @TunaLobster commented on GitHub (Nov 13, 2021): For each of you, are server and client the same version?
Author
Owner

@geekypathak21 commented on GitHub (Nov 13, 2021):

yup same version of barrier but different version of ubuntu

<!-- gh-comment-id:968101490 --> @geekypathak21 commented on GitHub (Nov 13, 2021): yup same version of barrier but different version of ubuntu
Author
Owner

@p1zzab0y commented on GitHub (Nov 15, 2021):

Same here, it still worked a couple days ago, both macs on same version 2.4.0

<!-- gh-comment-id:968431740 --> @p1zzab0y commented on GitHub (Nov 15, 2021): Same here, it still worked a couple days ago, both macs on same version 2.4.0
Author
Owner

@SweKalken commented on GitHub (Nov 16, 2021):

I've got the same issue. Same version on both computers but unable to connect.

<!-- gh-comment-id:970490450 --> @SweKalken commented on GitHub (Nov 16, 2021): I've got the same issue. Same version on both computers but unable to connect.
Author
Owner

@jakubvlk commented on GitHub (Nov 16, 2021):

EDIT: After disabling SSL in Settings on both client and server I am able to get Barrier running and it's working now.

Same problem here. I am stuck with "Barier is starting" on client. Server Windows 10 Pro 21H1 and client macOS Big Sur 11.5.2.

log:
[2021-11-16T20:36:40] INFO: starting client [2021-11-16T20:36:40] INFO: config file: /private/var/folders/ql/m8pm9qs50kgg2lcwfw6skh3r0000gn/T/Barrier.IBMJlU [2021-11-16T20:36:40] INFO: log level: INFO [2021-11-16T20:36:40] INFO: drag and drop enabled [2021-11-16T20:36:40] NOTE: started client [2021-11-16T20:36:40] NOTE: connecting to '192.168.0.153': 192.168.0.153:24800 [2021-11-16T20:36:40] INFO: OpenSSL 3.0.0 7 sep 2021 2021-11-16 20:36:40.246 barrierc[26799:367324] starting cocoa loop [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl error occurred (system call failure) [2021-11-16T20:36:40] ERROR: failed to connect secure socket [2021-11-16T20:36:55] WARNING: failed to connect to server: Timed out [2021-11-16T20:36:56] NOTE: connecting to '192.168.0.153': 192.168.0.153:24800 [2021-11-16T20:36:56] INFO: OpenSSL 3.0.0 7 sep 2021 [2021-11-16T20:36:56] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:56] ERROR: could not load client certificates [2021-11-16T20:36:56] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:56] ERROR: could not load client certificates [2021-11-16T20:36:56] ERROR: ssl error occurred (generic failure) [2021-11-16T20:36:56] ERROR: error:0A000126:SSL routines::unexpected eof while reading [2021-11-16T20:36:56] ERROR: failed to connect secure socket

<!-- gh-comment-id:970598099 --> @jakubvlk commented on GitHub (Nov 16, 2021): **EDIT:** After **disabling SSL** in Settings on **both client and server** I am able to get Barrier running and **it's working** now. Same problem here. I am stuck with "Barier is starting" on client. Server Windows 10 Pro 21H1 and client macOS Big Sur 11.5.2. log: `[2021-11-16T20:36:40] INFO: starting client [2021-11-16T20:36:40] INFO: config file: /private/var/folders/ql/m8pm9qs50kgg2lcwfw6skh3r0000gn/T/Barrier.IBMJlU [2021-11-16T20:36:40] INFO: log level: INFO [2021-11-16T20:36:40] INFO: drag and drop enabled [2021-11-16T20:36:40] NOTE: started client [2021-11-16T20:36:40] NOTE: connecting to '192.168.0.153': 192.168.0.153:24800 [2021-11-16T20:36:40] INFO: OpenSSL 3.0.0 7 sep 2021 2021-11-16 20:36:40.246 barrierc[26799:367324] starting cocoa loop [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:40] ERROR: could not load client certificates [2021-11-16T20:36:40] ERROR: ssl error occurred (system call failure) [2021-11-16T20:36:40] ERROR: failed to connect secure socket [2021-11-16T20:36:55] WARNING: failed to connect to server: Timed out [2021-11-16T20:36:56] NOTE: connecting to '192.168.0.153': 192.168.0.153:24800 [2021-11-16T20:36:56] INFO: OpenSSL 3.0.0 7 sep 2021 [2021-11-16T20:36:56] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:56] ERROR: could not load client certificates [2021-11-16T20:36:56] ERROR: ssl certificate doesn't exist: /Users/jakubvlk/Library/Application Support/barrier/SSL/Barrier.pem [2021-11-16T20:36:56] ERROR: could not load client certificates [2021-11-16T20:36:56] ERROR: ssl error occurred (generic failure) [2021-11-16T20:36:56] ERROR: error:0A000126:SSL routines::unexpected eof while reading [2021-11-16T20:36:56] ERROR: failed to connect secure socket`
Author
Owner

@bodhihawken commented on GitHub (Nov 17, 2021):

Can Confirm, getting this issue on Windows 10 -> Mac 10.15.4

Infinite, "Barrier is Starting"

<!-- gh-comment-id:971280799 --> @bodhihawken commented on GitHub (Nov 17, 2021): Can Confirm, getting this issue on Windows 10 -> Mac 10.15.4 Infinite, "Barrier is Starting"
Author
Owner

@SR-G commented on GitHub (Nov 19, 2021):

EDIT: After disabling SSL in Settings on both client and server I am able to get Barrier running and it's working now.

Thank you so much ! First installation of Barrier here (2.4.0, on WIN10 + ARCHLINUX) and nothing was working. After struggling 30 minutes, i was about to give up, but in fact it was that SSL setting (enabled by default) that was causing trouble.

<!-- gh-comment-id:974348003 --> @SR-G commented on GitHub (Nov 19, 2021): > **EDIT:** After **disabling SSL** in Settings on **both client and server** I am able to get Barrier running and **it's working** now. Thank you so much ! First installation of Barrier here (2.4.0, on WIN10 + ARCHLINUX) and nothing was working. After struggling 30 minutes, i was about to give up, but in fact it was that SSL setting (enabled by default) that was causing trouble.
Author
Owner

@JakubRakus commented on GitHub (Nov 25, 2021):

I've had exactly the same problem with SSL after upgrade to 2.4.0. It's working now with SSL off.

<!-- gh-comment-id:978901221 --> @JakubRakus commented on GitHub (Nov 25, 2021): I've had exactly the same problem with SSL after upgrade to 2.4.0. It's working now with SSL off.
Author
Owner

@hovanesgasparian commented on GitHub (Dec 1, 2021):

@JakubRakus How do you turn off SSL? My macOS client says SSL Fingerprint: Disabled, but I also get the same certificate does not exist error.

<!-- gh-comment-id:983953046 --> @hovanesgasparian commented on GitHub (Dec 1, 2021): @JakubRakus How do you turn off SSL? My macOS client says SSL Fingerprint: Disabled, but I also get the same certificate does not exist error.
Author
Owner

@SR-G commented on GitHub (Dec 1, 2021):

As simple as Menu "Barrier" > "Settings" and then uncheck the box in the middle under "Networking".

setting

<!-- gh-comment-id:984018849 --> @SR-G commented on GitHub (Dec 1, 2021): As simple as Menu "Barrier" > "Settings" and then uncheck the box in the middle under "Networking". ![setting](https://i.imgur.com/s2XuImO.png)
Author
Owner

@hovanesgasparian commented on GitHub (Dec 1, 2021):

@SR-G thank you! Can't believe I missed that before... regardless, it didn't help... it would just constantly try to connect, and reconnect, over and over without success.

<!-- gh-comment-id:984034338 --> @hovanesgasparian commented on GitHub (Dec 1, 2021): @SR-G thank you! Can't believe I missed that before... regardless, it didn't help... it would just constantly try to connect, and reconnect, over and over without success.
Author
Owner

@SR-G commented on GitHub (Dec 1, 2021):

For this setting to work, you have to :

  1. Apply the uncheck on all computers (not only the server one)
  2. Stop'n'restart all barrier programs

Of course maybe you are encountering a different issue in the end (but i would double check these two points).

<!-- gh-comment-id:984048072 --> @SR-G commented on GitHub (Dec 1, 2021): For this setting to work, you have to : 1. Apply the uncheck on all computers (not only the server one) 2. Stop'n'restart all barrier programs Of course maybe you are encountering a different issue in the end (but i would double check these two points).
Author
Owner

@Esquilli commented on GitHub (Dec 1, 2021):

Same thing is happening to me, but the SSL trick is not working for me.

<!-- gh-comment-id:984078479 --> @Esquilli commented on GitHub (Dec 1, 2021): Same thing is happening to me, but the SSL trick is not working for me.
Author
Owner

@dnet890 commented on GitHub (Dec 2, 2021):

I tried to turn off the SSL with the server in my Ubuntu PC and the client is Win10. But, it does not work

<!-- gh-comment-id:984351586 --> @dnet890 commented on GitHub (Dec 2, 2021): I tried to turn off the SSL with the server in my Ubuntu PC and the client is Win10. But, it does not work
Author
Owner

@mcwillzz commented on GitHub (Dec 6, 2021):

I was having the same issue with my OSX client stuck on 'Barrier is starting'. Disabling SSL by itself did not fix it, but disabling my VPN on both machines did. I'm not sure why, since Barrier is configured to be working over my local network. Once the connection was established, I could re-enable my VPN on both machines and it works without issue.

<!-- gh-comment-id:986387084 --> @mcwillzz commented on GitHub (Dec 6, 2021): I was having the same issue with my OSX client stuck on 'Barrier is starting'. Disabling SSL by itself did not fix it, but disabling my VPN on both machines did. I'm not sure why, since Barrier is configured to be working over my local network. Once the connection was established, I could re-enable my VPN on both machines and it works without issue.
Author
Owner

@mplorentz commented on GitHub (Dec 9, 2021):

It sounds like one problem is that Barrier is not generating its SSL certificates. That's why disabling SSL is working for some people. If you don't want to disable SSL you can generate the certificates yourself using the steps in this thread.

<!-- gh-comment-id:989899079 --> @mplorentz commented on GitHub (Dec 9, 2021): It sounds like one problem is that Barrier is not generating its SSL certificates. That's why disabling SSL is working for some people. If you don't want to disable SSL you can generate the certificates yourself using the steps in [this thread](https://github.com/debauchee/barrier/issues/231#issuecomment-962421337).
Author
Owner

@andremeiras commented on GitHub (Feb 14, 2022):

Hey guys,

In my case I unmarked this option but the problem wasn't with SSL.
Finally I solved just creating a barrier.sgc file and setting up manually the properties for the server and client.

@geekypathak21, in your answer, you didn't paste your log but I hope this will help you too.

  • First at all, enable the log level to DEBUG in your Barrier configurations to see the error.
  • Press F2 (to show log) and start your server. When you see in your log an ERROR, stop you server.
  • Search in log for the error. In my case was something wrong with the port 24800 (`:24800'). it was showing a special character (grave accent - &grave) before the port :24800, as you can see, but looking at my configs, it was correctly.

Try this:

Create a file named barrier.sgc with your file editor (notepad, sublime text, vscode, etc) and save in a local that you easily remember.

Into that, paste this and change the name of your server and client:

section: screens
	BARRIERSERVER:
	BARRIERCLIENT:
end

section: aliases
end

section: links
	BARRIERCLIENT:
		right = BARRIERSERVER
	BARRIERSERVER:
		left = BARRIERCLIENT
end

section: options
	relativeMouseMoves = false
	screenSaverSync = false
	win32KeepForeground = false
	clipboardSharing = true
	switchCorners = none
	switchCornerSize = 0
end

After that, in your Barrier, on the Server configuration, select the option to set your custom file and select the file saved before.

Start the server and see if it solves your problem too.

Hope this help you.

<!-- gh-comment-id:1038501497 --> @andremeiras commented on GitHub (Feb 14, 2022): Hey guys, In my case I unmarked this option but the problem wasn't with SSL. Finally I solved just creating a **barrier.sgc** file and setting up manually the properties for the server and client. @geekypathak21, in your answer, you didn't paste your log but I hope this will help you too. - First at all, enable the log level to DEBUG in your Barrier configurations to see the error. - Press F2 (to show log) and start your server. When you see in your log an ERROR, stop you server. - Search in log for the error. In my case was something wrong with the port 24800 (**`:24800'**). it was showing a special character (grave accent - &grave) before the port :24800, as you can see, but looking at my configs, it was correctly. Try this: Create a file named **barrier.sgc** with your file editor (notepad, sublime text, vscode, etc) and save in a local that you easily remember. Into that, paste this and change the name of your server and client: ``` section: screens BARRIERSERVER: BARRIERCLIENT: end section: aliases end section: links BARRIERCLIENT: right = BARRIERSERVER BARRIERSERVER: left = BARRIERCLIENT end section: options relativeMouseMoves = false screenSaverSync = false win32KeepForeground = false clipboardSharing = true switchCorners = none switchCornerSize = 0 end ``` After that, in your Barrier, on the Server configuration, select the option to set your custom file and select the file saved before. Start the server and see if it solves your problem too. Hope this help you.
Author
Owner

@geekypathak21 commented on GitHub (Feb 19, 2022):

It sounds like one problem is that Barrier is not generating its SSL certificates. That's why disabling SSL is working for some people. If you don't want to disable SSL you can generate the certificates yourself using the steps in this thread.

Thanks @mplorentz this is solving the issue I am closing this issue.
Thanks @andremeiras in my case disabling ssl worked.

<!-- gh-comment-id:1046023147 --> @geekypathak21 commented on GitHub (Feb 19, 2022): > It sounds like one problem is that Barrier is not generating its SSL certificates. That's why disabling SSL is working for some people. If you don't want to disable SSL you can generate the certificates yourself using the steps in [this thread](https://github.com/debauchee/barrier/issues/231#issuecomment-962421337). Thanks @mplorentz this is solving the issue I am closing this issue. Thanks @andremeiras in my case disabling ssl worked.
Author
Owner

@mplorentz commented on GitHub (Feb 19, 2022):

Shouldn't barrier generate the SSL certificate automatically? It seems like that's how it used to work, and this was a regression, so it seems like this issue should stay open until it is fixed.

<!-- gh-comment-id:1046041690 --> @mplorentz commented on GitHub (Feb 19, 2022): Shouldn't barrier generate the SSL certificate automatically? It seems like that's how it used to work, and this was a regression, so it seems like this issue should stay open until it is fixed.
Author
Owner

@geekypathak21 commented on GitHub (Feb 20, 2022):

Agree @mplorentz Reopening this issue barrier should generate certificate automatically.

<!-- gh-comment-id:1046250532 --> @geekypathak21 commented on GitHub (Feb 20, 2022): Agree @mplorentz Reopening this issue barrier should generate certificate automatically.
Author
Owner

@nisardevpro commented on GitHub (Apr 16, 2022):

I was facing the same problem. Fixed it by disabling the SSL from the setting.

<!-- gh-comment-id:1100608461 --> @nisardevpro commented on GitHub (Apr 16, 2022): I was facing the same problem. Fixed it by disabling the SSL from the setting.
Author
Owner

@vertexgamer commented on GitHub (May 16, 2022):

fucking finally, disabling ssl worked. Make it disabled by default, or i will sneak inside your house at night and write bugs on all of your projects :)

<!-- gh-comment-id:1128157723 --> @vertexgamer commented on GitHub (May 16, 2022): fucking finally, disabling ssl worked. Make it disabled by default, or i will sneak inside your house at night and write bugs on all of your projects :)
Author
Owner

@hannesdelbeke commented on GitHub (May 25, 2022):

Here is what I did when one of my clients didnt work.

update client to barrier 2.4 (server already was on 2.4)
this triggered both pc's asking for a new fingerprint/cert window
Then after renaming my client in the config, and updating the server config to match,
the SSL connection works again.

Curious if there is a manual way to trigger the refresh of the cert/fingerprint?

<!-- gh-comment-id:1136972240 --> @hannesdelbeke commented on GitHub (May 25, 2022): Here is what I did when one of my clients didnt work. update client to barrier 2.4 (server already was on 2.4) this triggered both pc's asking for a new fingerprint/cert window Then after renaming my client in the config, and updating the server config to match, the SSL connection works again. Curious if there is a manual way to trigger the refresh of the cert/fingerprint?
Author
Owner

@bobtelington commented on GitHub (Jun 3, 2022):

Version 2.4 on 2 Windows 10 machines was giving me the same connection issue. Turned off server and client, Disabled SSL on the server then the client. Started server, then the client. That seems to have solved the problem for me. Not sure if the order matters or not but hey it's worth a try. Hopefully, that helps.

<!-- gh-comment-id:1146195187 --> @bobtelington commented on GitHub (Jun 3, 2022): Version 2.4 on 2 Windows 10 machines was giving me the same connection issue. Turned off server and client, Disabled SSL on the server then the client. Started server, then the client. That seems to have solved the problem for me. Not sure if the order matters or not but hey it's worth a try. Hopefully, that helps.
Author
Owner

@drecdroid commented on GitHub (Jun 11, 2022):

Turning SSL is not secure. I had the same problem with Synergy, although it is not the same software, it should be similar if not the same for barrier.

  • Allow connections through port 24800 (sudo firewall-cmd --zone=FedoraWorkstation --add-service=synergy --permanent)
  • Install openssl (sudo dnf install openssl on Fedora)

I'll test this later using barrier.

<!-- gh-comment-id:1152969969 --> @drecdroid commented on GitHub (Jun 11, 2022): Turning SSL is not secure. I had the same problem with Synergy, although it is not the same software, it should be similar if not the same for barrier. - Allow connections through port 24800 (`sudo firewall-cmd --zone=FedoraWorkstation --add-service=synergy --permanent`) - Install openssl (`sudo dnf install openssl` on Fedora) I'll test this later using barrier.
Author
Owner

@Svedrin commented on GitHub (Aug 8, 2022):

I've had a similar issue. I set up barrier between a Windows server and a Ubuntu client without using SSL. Everything worked smoothly until I installed updates on the Ubuntu client. Then it failed to load client certs, so I tried to set up SSL without much success. After pulling my hair out for a few days, I got it to work by guessing that --disable-crypto might be an option that the client accepts (even though it isn't documented). I restarted the client with that option and it connected just fine.

Note that I tried to set up SSL using the OpenSSL commands that can be found all over the place, but the Barrier server just ignored everything and I couldn't get it to work no matter what I tried. It would be really helpful if both the client and the server would just generate everything they need automatically... 🙁

<!-- gh-comment-id:1207785960 --> @Svedrin commented on GitHub (Aug 8, 2022): I've had a similar issue. I set up barrier between a Windows server and a Ubuntu client without using SSL. Everything worked smoothly until I installed updates on the Ubuntu client. Then it failed to load client certs, so I tried to set up SSL without much success. After pulling my hair out for a few days, I got it to work by guessing that `--disable-crypto` might be an option that the client accepts (even though it isn't documented). I restarted the client with that option and it connected just fine. Note that I tried to set up SSL using the OpenSSL commands that can be found all over the place, but the Barrier server just ignored everything and I couldn't get it to work no matter what I tried. It would be really helpful if both the client and the server would just generate everything they need automatically... 🙁
Author
Owner

@unbeatendev commented on GitHub (Feb 8, 2023):

If you are still having issues, do this instead.

Disable SSL on all PC.
Copy the same port for all PC. I mean ensure all connected PC has the same port. This worked for me after trying all possible solutions for 2 days.

Also, I make sure the network is connected to the same wifi.

Screenshot 2023-02-08 at 10 27 19 AM
<!-- gh-comment-id:1422084500 --> @unbeatendev commented on GitHub (Feb 8, 2023): If you are still having issues, do this instead. Disable SSL on all PC. Copy the same port for all PC. I mean ensure all connected PC has the same port. This worked for me after trying all possible solutions for 2 days. Also, I make sure the network is connected to the same wifi. <img width="469" alt="Screenshot 2023-02-08 at 10 27 19 AM" src="https://user-images.githubusercontent.com/67667656/217451980-e18b823c-0b30-4c44-af9e-4ae7061be0bc.png">
Author
Owner

@robywoo commented on GitHub (Feb 23, 2023):

Mine is the same. I checked and unchecked the Enable SSL, both computers (Server is Ventura OS 13, Client Big Sur OS 11.7) are on the same port 24800 and both on same LAN via ethernet. Changed logging level to debug on both but no change. They have been working fine until today the client is not connecting and is stuck on "starting". Server is "running". Log shows Failed to connect to server - connection refused

<!-- gh-comment-id:1441125052 --> @robywoo commented on GitHub (Feb 23, 2023): Mine is the same. I checked and unchecked the Enable SSL, both computers (Server is Ventura OS 13, Client Big Sur OS 11.7) are on the same port 24800 and both on same LAN via ethernet. Changed logging level to debug on both but no change. They have been working fine until today the client is not connecting and is stuck on "starting". Server is "running". Log shows Failed to connect to server - connection refused
Author
Owner

@SlowHyper commented on GitHub (Mar 7, 2023):

Upgraded Ubuntu from 20.04 to 22.04 and barrier server was not working. I disabled SSL but still barrier was not working.
For anyone interested my problem was solved and SSL is now working fine, by logging in with an xorg session.
Maybe wayland support is the problem! I hope this helps.

<!-- gh-comment-id:1457767636 --> @SlowHyper commented on GitHub (Mar 7, 2023): Upgraded Ubuntu from 20.04 to 22.04 and barrier server was not working. I disabled SSL but still barrier was not working. For anyone interested my problem was solved and SSL is now working fine, by logging in with an xorg session. Maybe wayland support is the problem! I hope this helps.
Author
Owner

@waall commented on GitHub (Apr 5, 2023):

Remember, if you disable SSL im both system, you need to configure the exactly HOSTNAME of the CLIENT in your SERVER. :)
To view your hostname, type on the CLI:
🐧 Linux and 🥛 Windows: hostname

<!-- gh-comment-id:1496834088 --> @waall commented on GitHub (Apr 5, 2023): Remember, if you disable SSL im both system, you need to configure the exactly HOSTNAME of the CLIENT in your SERVER. :) To view your hostname, type on the CLI: 🐧 Linux and 🥛 Windows: **hostname**
Author
Owner

@sranjanB commented on GitHub (Apr 18, 2023):

Hi folks, I am using linux mint as my server and Windows10 as client, I have tried 2 tricks that worked for me.First of all SSL off kind of work to identify the server from client and then if you probably see below logs you should turn off auto config from client side provide server ip.Do not forget to configure server .
failed logs:
[2023-04-18T22:01:55] NOTE: client "swin" has disconnected
[2023-04-18T22:01:56] NOTE: accepted client connection
[2023-04-18T22:01:56] NOTE: disconnecting client "swin"
[2023-04-18T22:01:56] WARNING: unrecognised client name "swin", check server config
[2023-04-18T22:01:56] NOTE: client "swin" has disconnected
[2023-04-18T22:01:57] NOTE: accepted client connection
[2023-04-18T22:01:57] NOTE: disconnecting client "swin"

<!-- gh-comment-id:1513479938 --> @sranjanB commented on GitHub (Apr 18, 2023): Hi folks, I am using linux mint as my server and Windows10 as client, I have tried 2 tricks that worked for me.First of all SSL off kind of work to identify the server from client and then if you probably see below logs you should turn off auto config from client side provide server ip.Do not forget to configure server . failed logs: [2023-04-18T22:01:55] NOTE: client "swin" has disconnected [2023-04-18T22:01:56] NOTE: accepted client connection [2023-04-18T22:01:56] NOTE: disconnecting client "swin" [2023-04-18T22:01:56] WARNING: unrecognised client name "swin", check server config [2023-04-18T22:01:56] NOTE: client "swin" has disconnected [2023-04-18T22:01:57] NOTE: accepted client connection [2023-04-18T22:01:57] NOTE: disconnecting client "swin"
Author
Owner

@mikbuch commented on GitHub (May 29, 2023):

I had similar issue while using two Macs. I resolved it by creating an SSL key like that: https://github.com/debauchee/barrier/issues/1609#issuecomment-1066938159 on one machine, and moving it to the same location on the other machine (with AirDrop).

<!-- gh-comment-id:1567573879 --> @mikbuch commented on GitHub (May 29, 2023): I had similar issue while using two Macs. I resolved it by creating an SSL key like that: https://github.com/debauchee/barrier/issues/1609#issuecomment-1066938159 on one machine, and moving it to the same location on the other machine (with AirDrop).
Author
Owner

@za-ova commented on GitHub (Feb 15, 2024):

so when i opened the log on the client it said that the server refuses client with name debian after a while i realized that i need to add an alias with the name debian to my configuration so it would accept the client (make sure that the device name is different than the alias)

Screenshot 2024-02-15 112927

after this it connected just fine but the whenever the mouse enters the other screen it stops working for some reason my internet connection is pretty bad rn so it might be that

Edit:i forgot to mention that the server is windows 11 and the client is debian (@sranjanB this should work for you "i hope")
Edit2: i tried using the config file method but it refused to read it

<!-- gh-comment-id:1945692153 --> @za-ova commented on GitHub (Feb 15, 2024): so when i opened the log on the client it said that the server refuses client with name debian after a while i realized that i need to add an alias with the name debian to my configuration so it would accept the client (make sure that the device name is different than the alias) ![Screenshot 2024-02-15 112927](https://github.com/debauchee/barrier/assets/160117407/2e61ea56-8bbf-4d56-b1a5-4cc75c9048cf) after this it connected just fine but the whenever the mouse enters the other screen it stops working for some reason my internet connection is pretty bad rn so it might be that Edit:i forgot to mention that the server is windows 11 and the client is debian (@sranjanB this should work for you "i hope") Edit2: i tried using the config file method but it refused to read it
Author
Owner

@cristianvnica commented on GitHub (Dec 20, 2024):

@za-ova worked for me, thank you!

<!-- gh-comment-id:2556628401 --> @cristianvnica commented on GitHub (Dec 20, 2024): @za-ova worked for me, thank you!
Author
Owner

@vadaysakiv commented on GitHub (Apr 29, 2025):

for me , i me 2 things works disabling ssl and using the corrent name for the devices

<!-- gh-comment-id:2839213297 --> @vadaysakiv commented on GitHub (Apr 29, 2025): for me , i me 2 things works disabling ssl and using the corrent name for the devices
Author
Owner

@nbolton commented on GitHub (Apr 29, 2025):

Please try Deskflow or Input Leap as Barrier is no longer in development.

https://github.com/deskflow/deskflow
https://github.com/input-leap/input-leap

Both are compatible with Barrier client/server so you can try on one of your computers.

If this is still an issue in those projects, we would appreciate a cross-post of this issue.

Not sure which to use? The 'Insights' tab of each project may help you decide.

<!-- gh-comment-id:2840167246 --> @nbolton commented on GitHub (Apr 29, 2025): Please try Deskflow or Input Leap as Barrier is no longer in development. https://github.com/deskflow/deskflow https://github.com/input-leap/input-leap Both are compatible with Barrier client/server so you can try on one of your computers. If this is still an issue in those projects, we would appreciate a cross-post of this issue. Not sure which to use? The 'Insights' tab of each project may help you decide.
Author
Owner

@vadaysakiv commented on GitHub (Apr 29, 2025):

@nbolton great timing, yes barrier work great with xfce but after that tool has limitation for wayland now, I tried the input leap that also is not working, now I am currently trying deskflow

<!-- gh-comment-id:2840177504 --> @vadaysakiv commented on GitHub (Apr 29, 2025): @nbolton great timing, yes barrier work great with xfce but after that tool has limitation for wayland now, I tried the input leap that also is not working, now I am currently trying deskflow
Author
Owner

@nbolton commented on GitHub (Apr 29, 2025):

@nbolton great timing, yes barrier work great with xfce but after that tool has limitation for wayland now, I tried the input leap that also is not working, now I am currently trying deskflow

Thanks for the update. Deskflow is leading edge, so it exclusively requires libei for Wayland support, whereas Input Leap is legacy so it supports XWayland (a Wayland extension for legacy apps that runs a little X server for those cases in which X is really needed).

<!-- gh-comment-id:2840193911 --> @nbolton commented on GitHub (Apr 29, 2025): > [@nbolton](https://github.com/nbolton) great timing, yes barrier work great with xfce but after that tool has limitation for wayland now, I tried the input leap that also is not working, now I am currently trying deskflow Thanks for the update. Deskflow is leading edge, so it exclusively requires `libei` for Wayland support, whereas Input Leap is legacy so it supports XWayland (a Wayland extension for legacy apps that runs a little X server for those cases in which X is really needed).
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/barrier#1097
No description provided.