[GH-ISSUE #618] while working perfectly fine, Barrier switches from Server to Client mode upon opening the application, and I can no longer switch to the client screen until I prod it a bit. #486

New issue

Open

opened 2026-05-05 06:31:02 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:31:02 -06:00

Owner

Originally created by @mspreij on GitHub (Apr 8, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/618

Operating Systems

Server: Windows 10, version 1909, build 18363.720
Client: macOS High Sierra (10.13.6)

Barrier Version

Mac: 2.3.2-Release-210c2b70
Win: 2.3.2-snapshot-210c2b70

Steps to reproduce bug

working situation, but I want to temporarily disable it, so I
open the application on Windows (the server)

What now happens is that the window opens with "Client" selected, and Barrier no longer does its magic, the mouse stops at the screen edge.
To fix it I have to:

select the "Server" checkbox
click "Stop", and click "Start"

And then everything works again.
A second workaround is not closing the window, but minimizing it instead.

Other info

Is there a way to work around it? Yes! \o/ (as described above)
Does this bug prevent you from using Barrier entirely? No, absolutely not.
When did the problem start to occur? Maybe when I switched the server with the client? Initially the Mac was the server, and Windows the client.
I've tried both "Configure interactively" and "Use existing configuration" but it makes no difference.
Windows is also occasionally connected to a VPN, but its connection status does not seem to make a difference.

I have attached the Windows/Server log from the point when I open the Barrier application during a working session. There are a lot of linebreaks in weird places, I have no idea how they get in there but I saw it every time I looked at that log. The Windows IP address is 192.168.178.14 aka HAL-9000. Following this one, 1 or 2 other offline-range IP address(es) are displayed in the Barrier window as well, probably related to the VPN it's sometimes on.
I've also attached the Mac/Client log from the same time, its IP address is 192.168.178.10 but I don't see that in the log, it's referred to as Hyperion.local.

barrier_windows.log
barrier_macos.log

Finally I would like to state that when it works, 99+% of the time, it's Friggin' Awesome.

Originally created by @mspreij on GitHub (Apr 8, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/618 ### Operating Systems ### Server: Windows 10, version 1909, build 18363.720 Client: macOS High Sierra (10.13.6) ### Barrier Version ### Mac: 2.3.2-Release-210c2b70 Win: 2.3.2-snapshot-210c2b70 ### Steps to reproduce bug ### 0. working situation, but I want to temporarily disable it, so I 1. open the application on Windows (the server) What now happens is that the window opens with "Client" selected, and Barrier no longer does its magic, the mouse stops at the screen edge. To fix it I have to: 1. select the "Server" checkbox 2. click "Stop", and click "Start" And then everything works again. A second workaround is *not* closing the window, but minimizing it instead. ### Other info ### * Is there a way to work around it? Yes! \o/ (as described above) * Does this bug prevent you from using Barrier entirely? No, absolutely not. * When did the problem start to occur? Maybe when I switched the server with the client? Initially the Mac was the server, and Windows the client. * I've tried both "Configure interactively" and "Use existing configuration" but it makes no difference. * Windows is also occasionally connected to a VPN, but its connection status does not seem to make a difference. I have attached the Windows/Server log from the point when I open the Barrier application during a working session. There are a lot of linebreaks in weird places, I have no idea how they get in there but I saw it every time I looked at that log. The Windows IP address is `192.168.178.14` aka `HAL-9000`. Following this one, 1 or 2 other offline-range IP address(es) *are* displayed in the Barrier window as well, probably related to the VPN it's sometimes on. I've also attached the Mac/Client log from the same time, its IP address is `192.168.178.10` but I don't see that in the log, it's referred to as `Hyperion.local`. [barrier_windows.log](https://github.com/debauchee/barrier/files/4451697/barrier_windows.log) [barrier_macos.log](https://github.com/debauchee/barrier/files/4451699/barrier_macos.log) Finally I would like to state that when it works, 99+% of the time, it's *Friggin' Awesome*.

gitea-mirror commented

2026-05-05 06:31:07 -06:00

Author

Owner

@mspreij commented on GitHub (Apr 10, 2020):

And in updated news.. it doesn't do this today (yes I did reboot but I also rebooted before so it's not just that.)

If you need me to test anything, feel free to yell.

@mspreij commented on GitHub (Apr 10, 2020): And in updated news.. it doesn't do this today (yes I did reboot but I also rebooted before so it's not *just* that.) If you need me to test anything, feel free to yell.

gitea-mirror commented

2026-05-05 06:31:09 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 24, 2020):

This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions[bot] commented on GitHub (Sep 24, 2020): This issue has been automatically marked as stale due to inactivity. It will be closed if no further activity occurs. Thank you for your contributions.

gitea-mirror commented

2026-05-05 06:31:11 -06:00

Author

Owner

@p12tic commented on GitHub (Jan 10, 2021):

@mspreij Are you still using Barrier in some way? I could help to try to debug this.

@p12tic commented on GitHub (Jan 10, 2021): @mspreij Are you still using Barrier in some way? I could help to try to debug this.