[GH-ISSUE #1571] "Barrier is starting" - bad error handling, the Log window is your friend #1180

Open
opened 2026-05-05 07:34:06 -06:00 by gitea-mirror · 0 comments
Owner

Originally created by @maf-soft on GitHub (Feb 17, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1571

What happened?

Barrier is a great help and I got it to work from Windows 11 to MacOS Monterey. However, the user experience in case of problems is bad, it took me some time, and a less experienced user would have given up for sure.

If the error handling is not improved, at least there should be some more hints here. "The log window is your friend in case of problems" could be the first hint. Not everyone is used to read log files.

Examples:

  • It could not be started on latest MacOS Monterey, "developer cannot be verified". How to skip this check is really hidden in the system and hard to find. So, first I tried older versions without success, before I found that workaround.
  • "Barrier is starting" on all sorts of problems. Why not display more info what it's doing?
  • I had to find the SSL option on client and server and switch it off.
  • Sometimes the UI hung with unknown reason, happened on both systems.
  • I tried to add the server screen twice, because it has 2 screens. Ok, my fault, but the log message "cannot load config file" is bad for this case.

Version

v2.4.0

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)

Linux, Windows, macOS

What OS versions are you using?

Server Windows 11, Client MacOS Monterey (M1)

Relevant log output

No response

Any other information

No response

Originally created by @maf-soft on GitHub (Feb 17, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1571 ### What happened? Barrier is a great help and I got it to work from Windows 11 to MacOS Monterey. However, the user experience in case of problems is bad, it took me some time, and a less experienced user would have given up for sure. If the error handling is not improved, at least there should be some more hints [here](https://github.com/debauchee/barrier#usage). "The log window is your friend in case of problems" could be the first hint. Not everyone is used to read log files. Examples: - It could not be started on latest MacOS Monterey, "developer cannot be verified". How to skip this check is really hidden in the system and hard to find. So, first I tried older versions without success, before I found that workaround. - "Barrier is starting" on all sorts of problems. Why not display more info what it's doing? - I had to find the SSL option on client and server and switch it off. - Sometimes the UI hung with unknown reason, happened on both systems. - I tried to add the server screen twice, because it has 2 screens. Ok, my fault, but the log message "cannot load config file" is bad for this case. ### Version v2.4.0 ### 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) Linux, Windows, macOS ### What OS versions are you using? Server Windows 11, Client MacOS Monterey (M1) ### Relevant log output _No response_ ### Any other information _No response_
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#1180
No description provided.