github-starred/barrier

Fork 0

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

[GH-ISSUE #566] Dash symbol is not recognized as valid screen name in interactive server cofiguration #443

New issue

Open

opened 2026-05-05 06:23:38 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 06:23:38 -06:00

Owner

Originally created by @elig0n on GitHub (Feb 15, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/566

Operating Systems

Server: Windows 10
Client: Linux

Barrier Version

2.3.2-snapshot-210c2b70

Steps to reproduce bug

When using "Configure interactively" having my hostname set under "Settings->Screen name" and Reloading leads to the log message "FATAL: unknown screen name [MY-HOSTNAME]".
Only after saving my settings to a file and explicitly choosing it with "Use existing configuration" would it then work.

Note: I came to notice this after first changing my screen name to something else, then back again to my hostname at which point saw it wasn't accepterd anymore.
I also tried various "grid" configurations with and without aliases at that time to no avail.

This also solved all connectivity issues I had with my client.

Originally created by @elig0n on GitHub (Feb 15, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/566 ### Operating Systems ### Server: Windows 10 Client: Linux ### Barrier Version ### 2.3.2-snapshot-210c2b70 ### Steps to reproduce bug ### When using "Configure interactively" having my hostname set under "Settings->Screen name" and Reloading leads to the log message "FATAL: unknown screen name [MY-HOSTNAME]". Only after saving my settings to a file and explicitly choosing it with "Use existing configuration" would it then work. Note: I came to notice this after first changing my screen name to something else, then back again to my hostname at which point saw it wasn't accepterd anymore. I also tried various "grid" configurations with and without aliases at that time to no avail. This also solved all connectivity issues I had with my client.

gitea-mirror added the

bug

label 2026-05-05 06:23:38 -06:00

gitea-mirror commented

2026-05-05 06:23:43 -06:00

Author

Owner

@the-wes commented on GitHub (Mar 3, 2020):

This usually happens when someone changes their hostname after the initial install and setup of Barrier.

The setup process involves Barrier adding a screen to the config grid with the host system's hostname - the default "screen name" used by Barrier. If this changes later, it must also be changed to the same name in the grid config screen or the symptoms described here will result.

This can also happen when host names and screen names contain certain characters - especially a dash (-) character. This seems to throw the config parser off and results in errors similar to this.

If the process you observed is different from what I described above, please help me to understand more clearly so we can address the issue once we get to a point where we can put resources towards it.

@the-wes commented on GitHub (Mar 3, 2020): This usually happens when someone changes their hostname after the initial install and setup of Barrier. The setup process involves Barrier adding a screen to the config grid with the host system's hostname - the default "screen name" used by Barrier. If this changes later, it must also be changed to the same name in the grid config screen or the symptoms described here will result. This can also happen when host names and screen names contain certain characters - especially a dash (-) character. This seems to throw the config parser off and results in errors similar to this. If the process you observed is different from what I described above, please help me to understand more clearly so we can address the issue once we get to a point where we can put resources towards it.

gitea-mirror commented

2026-05-05 06:23:46 -06:00

Author

Owner

@jrd commented on GitHub (Mar 30, 2020):

Ahhh the dash − was the problem for me.

@jrd commented on GitHub (Mar 30, 2020): Ahhh the **dash −** was the problem for me.

gitea-mirror commented

2026-05-05 06:23:49 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 28, 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 28, 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:23:51 -06:00

Author

Owner

@sabarnix commented on GitHub (Jul 1, 2022):

barrier is not detecting the new hostname. How to reset the configuration?

@sabarnix commented on GitHub (Jul 1, 2022): barrier is not detecting the new hostname. How to reset the configuration?

No labels

Rows
Columns