[GH-ISSUE #704] Auto config checked still application complains about hostname not filled #561

New issue

Closed

opened 2026-05-05 06:41:04 -06:00 by gitea-mirror · 4 comments

gitea-mirror commented

2026-05-05 06:41:04 -06:00

Owner

Originally created by @jmartens on GitHub (May 29, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/704

Operating Systems

Server: Windows 10 Professional 1909

Client: Ubuntu 20.04 LTS

Barrier Version

Server: 2.3.2-snapshot-210cb270
Client: 2.3.2-Release-00000000 (from ubuntu apt)

Steps to reproduce bug

Start Barrier on server and configure client host name as usual
Start Barrier on client
Do not modify config, make sure Auto config is checked and no hostname entered
Click Start
Observe error message with title: Hostname is empty and text: Pleas filll in a hostname for the barrier client to connect to.

Other info

Immediately after install, no manual config on client, workaround is off-course to enter the server IP hostname and not use Auto config, but that defeats the purpose of Auto config IMHO

Originally created by @jmartens on GitHub (May 29, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/704 ### Operating Systems ### Server: Windows 10 Professional 1909 Client: Ubuntu 20.04 LTS ### Barrier Version ### Server: 2.3.2-snapshot-210cb270 Client: 2.3.2-Release-00000000 (from ubuntu apt) ### Steps to reproduce bug ### 1. Start Barrier on server and configure client host name as usual 2. Start Barrier on client 3. Do not modify config, make sure Auto config is checked and no hostname entered 4. Click Start 5. Observe error message with title: Hostname is empty and text: Pleas filll in a hostname for the barrier client to connect to. ### Other info ### Immediately after install, no manual config on client, workaround is off-course to enter the server IP hostname and not use Auto config, but that defeats the purpose of Auto config IMHO

gitea-mirror closed this issue

2026-05-05 06:41:06 -06:00

gitea-mirror commented

2026-05-05 06:41:09 -06:00

Author

Owner

@jmartens commented on GitHub (May 29, 2020):

Just tried the other way around with same versions and behavior is the same, so also present in latest Windows release as can be seen in below screenshot (ciphers and other privacy info removed):

@jmartens commented on GitHub (May 29, 2020): Just tried the other way around with same versions and behavior is the same, so also present in latest Windows release as can be seen in below screenshot (ciphers and other privacy info removed): ![image](https://user-images.githubusercontent.com/593327/83233994-de49df80-a18f-11ea-9c0b-c2074851db54.png)

gitea-mirror commented

2026-05-05 06:41:11 -06:00

Author

Owner

@jmartens commented on GitHub (May 29, 2020):

When a hostname is entered and Auto config is checked it does work, however when auto config is checked the Server IP field is disabled/grayed out and a hostname cannot be entered.

Two possible options:

(preffered, as most intuitive IMHO) Do not require a Server IP when Auto config is enabled, ignore the Server IP field (and it's perhaps configured value) and don't complain about it and try to discover the server and connect when found
Do not disable Server IP field when checking auto config and prompt user for missing Server IP, of required for Auto config additional features (if any)

@jmartens commented on GitHub (May 29, 2020): When a hostname is entered and Auto config is checked it does work, however when auto config is checked the Server IP field is disabled/grayed out and a hostname cannot be entered. Two possible options: 1. (preffered, as most intuitive IMHO) Do not require a Server IP when Auto config is enabled, ignore the Server IP field (and it's perhaps configured value) and don't complain about it and try to discover the server and connect when found 2. Do not disable Server IP field when checking auto config and prompt user for missing Server IP, of required for Auto config additional features (if any)

gitea-mirror commented

2026-05-05 06:41:13 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 20, 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 20, 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:41:14 -06:00

Author

Owner

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

This has been fixed in #706.

@p12tic commented on GitHub (Jan 10, 2021): This has been fixed in #706.