Barrier: Interactive server cofiguration don't recognize actual hostname as valid screen name

Created on 15 Feb 2020 · 3Comments · Source: debauchee/barrier

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.

bug no-issue-activity

Source

elig0n

All 3 comments

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 on 3 Mar 2020

👀1 👍1

Ahhh the dash − was the problem for me.

jrd on 31 Mar 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.