[GH-ISSUE #1588] unable to change hostname #1184

New issue

Closed

opened 2026-05-05 07:34:14 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 07:34:14 -06:00

Owner

Originally created by @ma3252788 on GitHub (Feb 28, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1588

What happened?

I cannot modify the hostname of the client, even if I have modified the name of the machine in the computer properties.

Win11

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)

Windows

What OS versions are you using?

Win11

Relevant log output

No response

Any other information

No response

Originally created by @ma3252788 on GitHub (Feb 28, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1588 ### What happened? I cannot modify the hostname of the client, even if I have modified the name of the machine in the computer properties. Win11 ### 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) Windows ### What OS versions are you using? Win11 ### Relevant log output _No response_ ### Any other information _No response_

gitea-mirror closed this issue

2026-05-05 07:34:16 -06:00

gitea-mirror commented

2026-05-05 07:34:19 -06:00

Author

Owner

@ma3252788 commented on GitHub (Feb 28, 2022):

Because the name used on my original computer contains Chinese, I can't connect. So I want to change the hostname to English, but I can't.

@ma3252788 commented on GitHub (Feb 28, 2022): Because the name used on my original computer contains Chinese, I can't connect. So I want to change the hostname to English, but I can't.

gitea-mirror commented

2026-05-05 07:34:22 -06:00

Author

Owner

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

how did you resolve this?

@sabarnix commented on GitHub (Jul 1, 2022): how did you resolve this?