github-starred/barrier

Fork 0

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

[GH-ISSUE #1641] New Client disconnected #1210

New issue

Open

opened 2026-05-05 07:36:43 -06:00 by gitea-mirror · 11 comments

gitea-mirror commented

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

Owner

Originally created by @feloau on GitHub (Apr 8, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1641

What happened?

started server (IPv4/IPv6), waiting for clients
2022-04-08 19:26:34.973639-0400 barriers[2184:163893] starting cocoa loop
[2022-04-08T19:26:48] NOTE: accepted client connection
[2022-04-08T19:26:48] NOTE: new client disconnected
[2022-04-08T19:27:04] NOTE: accepted client connection
[2022-04-08T19:27:04] NOTE: new client disconnected
[2022-04-08T19:27:20] NOTE: accepted client connection
[2022-04-08T19:27:20] NOTE: new client disconnected
[2022-04-08T19:27:36] NOTE: accepted client connection
[2022-04-08T19:27:36] NOTE: new client disconnected
[2022-04-08T19:27:53] NOTE: accepted client connection
[2022-04-08T19:27:53] NOTE: new client disconnected
[2022-04-08T19:28:08] NOTE: accepted client connection
[2022-04-08T19:28:08] NOTE: new client disconnected
[2022-04-08T19:28:24] NOTE: accepted client connection
[2022-04-08T19:28:24] NOTE: new client disconnected

Version

v2.3.4

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)

Windows

What OS versions are you using?

Monterey 12.2.1 (Server)

Windows 11 (client)

Relevant log output

No response

Any other information

I tried with barrier 2.4, and it has the same problem

Originally created by @feloau on GitHub (Apr 8, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1641 ### What happened? started server (IPv4/IPv6), waiting for clients 2022-04-08 19:26:34.973639-0400 barriers[2184:163893] starting cocoa loop [2022-04-08T19:26:48] NOTE: accepted client connection [2022-04-08T19:26:48] NOTE: new client disconnected [2022-04-08T19:27:04] NOTE: accepted client connection [2022-04-08T19:27:04] NOTE: new client disconnected [2022-04-08T19:27:20] NOTE: accepted client connection [2022-04-08T19:27:20] NOTE: new client disconnected [2022-04-08T19:27:36] NOTE: accepted client connection [2022-04-08T19:27:36] NOTE: new client disconnected [2022-04-08T19:27:53] NOTE: accepted client connection [2022-04-08T19:27:53] NOTE: new client disconnected [2022-04-08T19:28:08] NOTE: accepted client connection [2022-04-08T19:28:08] NOTE: new client disconnected [2022-04-08T19:28:24] NOTE: accepted client connection [2022-04-08T19:28:24] NOTE: new client disconnected ### Version v2.3.4 ### 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) Windows ### What OS versions are you using? Monterey 12.2.1 (Server) Windows 11 (client) ### Relevant log output _No response_ ### Any other information I tried with barrier 2.4, and it has the same problem

gitea-mirror commented

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

Author

Owner

@grobmeier commented on GitHub (Apr 26, 2022):

I hade the same, when log said ssl certificates are not found. When I disabled them in my safe network, it worked.

@grobmeier commented on GitHub (Apr 26, 2022): I hade the same, when log said ssl certificates are not found. When I disabled them in my safe network, it worked.

gitea-mirror commented

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

Author

Owner

@Valentin-Bio-zz commented on GitHub (Aug 15, 2022):

is this resolved?

@Valentin-Bio-zz commented on GitHub (Aug 15, 2022): is this resolved?

gitea-mirror commented

2026-05-05 07:36:49 -06:00

Author

Owner

@lilasquared commented on GitHub (Oct 4, 2022):

I just ran into this and it was due to a ghost instance of synergy running on the client machine. Once I got rid of it then everything started to work again

@lilasquared commented on GitHub (Oct 4, 2022): I just ran into this and it was due to a ghost instance of synergy running on the client machine. Once I got rid of it then everything started to work again

gitea-mirror commented

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

Author

Owner

@julpod commented on GitHub (Nov 3, 2022):

same issue here with two macoss (macbook pro and imac) both under macos 12.6

@julpod commented on GitHub (Nov 3, 2022): same issue here with two macoss (macbook pro and imac) both under macos 12.6

gitea-mirror commented

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

Author

Owner

@Colonater commented on GitHub (Apr 28, 2023):

Same issue between steam deck and Windows

@Colonater commented on GitHub (Apr 28, 2023): Same issue between steam deck and Windows

gitea-mirror commented

2026-05-05 07:36:53 -06:00

Author

Owner

@hotfistdotcom commented on GitHub (May 2, 2023):

I hade the same, when log said ssl certificates are not found. When I disabled them in my safe network, it worked.

Same issue, can you go over how you did this?

@hotfistdotcom commented on GitHub (May 2, 2023): > I hade the same, when log said ssl certificates are not found. When I disabled them in my safe network, it worked. Same issue, can you go over how you did this?

gitea-mirror commented

2026-05-05 07:36:53 -06:00

Author

Owner

@vsenderov commented on GitHub (Aug 16, 2023):

In my case, one of the devices had "Enable SSL" (Windows client) and the Linux server did not. (In Change Settings F4). I un-clicked it both-ways since I use it in a private network behind a firewall, and it worked. Presumably it would work if it is on on both devices.

@vsenderov commented on GitHub (Aug 16, 2023): In my case, one of the devices had "Enable SSL" (Windows client) and the Linux server did not. (In Change Settings F4). I un-clicked it both-ways since I use it in a private network behind a firewall, and it worked. Presumably it would work if it _is on_ on both devices.

gitea-mirror commented

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

Author

Owner

@CreativilyInsane commented on GitHub (Jan 16, 2025):

i have a one mac I'm unable to disable ssl in mac 10.13

@CreativilyInsane commented on GitHub (Jan 16, 2025): i have a one mac I'm unable to disable ssl in mac 10.13

gitea-mirror commented

2026-05-05 07:36:55 -06:00

Author

Owner

@nbolton commented on GitHub (Jan 16, 2025):

@CreativilyInsane 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

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

@nbolton commented on GitHub (Jan 16, 2025): @CreativilyInsane 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 If this is still an issue in those projects, we would appreciate a cross-post of this issue.

gitea-mirror commented

2026-05-05 07:36:55 -06:00

Author

Owner

@MhL5 commented on GitHub (Jan 31, 2025):

i had the same issue

[2025-01-31T15:31:52] NOTE: accepted client connection
[2025-01-31T15:31:52] NOTE: new client disconnected

turning ssl off on both windows 11 and macos sequoia fixed it

@MhL5 commented on GitHub (Jan 31, 2025): i had the same issue ``` [2025-01-31T15:31:52] NOTE: accepted client connection [2025-01-31T15:31:52] NOTE: new client disconnected ``` turning ssl off on both `windows 11` and `macos sequoia` fixed it

gitea-mirror commented

2026-05-05 07:36:57 -06:00

Author

Owner

@DrzwiPercepcji commented on GitHub (Dec 13, 2025):

I was able to make it work by copying the local-fingerprint file from the server to the client and renaming it to trusted-servers. It looks like, for some reason, the client did not create this file. I saw in the logs that the server fingerprint could not be validated. I use Linux as a server and Windows as a client.

@DrzwiPercepcji commented on GitHub (Dec 13, 2025): I was able to make it work by copying the `local-fingerprint` file from the server to the client and renaming it to `trusted-servers`. It looks like, for some reason, the client did not create this file. I saw in the logs that the server fingerprint could not be validated. I use Linux as a server and Windows as a client.