[GH-ISSUE #829] New installation, windows server problem #658

Closed
opened 2026-05-05 06:51:45 -06:00 by gitea-mirror · 8 comments
Owner

Originally created by @RealLordK1 on GitHub (Aug 10, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/829

Operating Systems

Server: Windows 10 (2004)

Client: Linux Mint 20 Ulyana

Barrier Version

2.3.3-release-3395cca9

Steps to reproduce bug

Every time I launch the server, I have an error telling me that the temporary configuration file required to start barrier can not be written. Trying to change the conf file path did not help.

Other info

  • Does this bug prevent you from using Barrier entirely? Yes

Here is the log with "configure interactively" :
[2020-08-10T13:18:18] INFO: starting server
[2020-08-10T13:18:19] INFO: config file:
[2020-08-10T13:18:19] INFO: log level: INFO
[2020-08-10T13:18:19] INFO: service command updated
[2020-08-10T13:18:19] INFO: starting new process as privileged user
[2020-08-10T13:18:19] INFO: drag and drop enabled
barriers.exe: no configuration available
[2020-08-10T13:18:20] ERROR: failed to launch, error: process immediately stopped
[2020-08-10T13:18:20] INFO: backing off, wait=2s, failures=1
[2020-08-10T13:18:22] INFO: starting new process as privileged user
[2020-08-10T13:18:22] INFO: drag and drop enabled
barriers.exe: no configuration available

Here is the log with a conf file in another path :
[2020-08-10T13:19:28] INFO: starting server
[2020-08-10T13:19:28] INFO: config file: K:/Téléchargements/conf.sgc
[2020-08-10T13:19:28] INFO: log level: INFO
[2020-08-10T13:19:28] INFO: service command updated
[2020-08-10T13:19:29] INFO: starting new process as privileged user
[2020-08-10T13:19:29] INFO: drag and drop enabled
barriers.exe: no configuration available
[2020-08-10T13:19:30] ERROR: failed to launch, error: process immediately stopped
[2020-08-10T13:19:30] INFO: backing off, wait=2s, failures=1
[2020-08-10T13:19:32] INFO: starting new process as privileged user
[2020-08-10T13:19:32] INFO: drag and drop enabled
barriers.exe: no configuration available

Originally created by @RealLordK1 on GitHub (Aug 10, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/829 ### Operating Systems ### Server: Windows 10 (2004) Client: Linux Mint 20 Ulyana ### Barrier Version ### 2.3.3-release-3395cca9 ### Steps to reproduce bug ### Every time I launch the server, I have an error telling me that the temporary configuration file required to start barrier can not be written. Trying to change the conf file path did not help. ### Other info ### * Does this bug prevent you from using Barrier entirely? Yes Here is the log with "configure interactively" : [2020-08-10T13:18:18] INFO: starting server [2020-08-10T13:18:19] INFO: config file: [2020-08-10T13:18:19] INFO: log level: INFO [2020-08-10T13:18:19] INFO: service command updated [2020-08-10T13:18:19] INFO: starting new process as privileged user [2020-08-10T13:18:19] INFO: drag and drop enabled barriers.exe: no configuration available [2020-08-10T13:18:20] ERROR: failed to launch, error: process immediately stopped [2020-08-10T13:18:20] INFO: backing off, wait=2s, failures=1 [2020-08-10T13:18:22] INFO: starting new process as privileged user [2020-08-10T13:18:22] INFO: drag and drop enabled barriers.exe: no configuration available Here is the log with a conf file in another path : [2020-08-10T13:19:28] INFO: starting server [2020-08-10T13:19:28] INFO: config file: K:/Téléchargements/conf.sgc [2020-08-10T13:19:28] INFO: log level: INFO [2020-08-10T13:19:28] INFO: service command updated [2020-08-10T13:19:29] INFO: starting new process as privileged user [2020-08-10T13:19:29] INFO: drag and drop enabled barriers.exe: no configuration available [2020-08-10T13:19:30] ERROR: failed to launch, error: process immediately stopped [2020-08-10T13:19:30] INFO: backing off, wait=2s, failures=1 [2020-08-10T13:19:32] INFO: starting new process as privileged user [2020-08-10T13:19:32] INFO: drag and drop enabled barriers.exe: no configuration available
gitea-mirror 2026-05-05 06:51:45 -06:00
Author
Owner

@Colanth commented on GitHub (Aug 15, 2020):

No response yet? Add another Windows 10 19041-191206-1406 installation of Barrier 2.3.3 release-d-186548a with exactly the same error message. (Also tried making it writable with no results.) Clients on Ubuntu and Raspbian seem to set up properly, but now I have 2 keyboards, 2 mice and a VNC to Rasberry. It sure would be nice (even worth a contribution) to get this working on all 3 computers.

<!-- gh-comment-id:674452813 --> @Colanth commented on GitHub (Aug 15, 2020): No response yet? Add another Windows 10 19041-191206-1406 installation of Barrier 2.3.3 release-d-186548a with exactly the same error message. (Also tried making it writable with no results.) Clients on Ubuntu and Raspbian seem to set up properly, but now I have 2 keyboards, 2 mice and a VNC to Rasberry. It sure would be nice (even worth a contribution) to get this working on all 3 computers.
Author
Owner

@jsantosdias commented on GitHub (Sep 11, 2020):

I have the same issue:
"barriers.exe: no configuration available"
What can I do?

<!-- gh-comment-id:690988671 --> @jsantosdias commented on GitHub (Sep 11, 2020): I have the same issue: "barriers.exe: no configuration available" What can I do?
Author
Owner

@jsantosdias commented on GitHub (Sep 11, 2020):

So figured out that the problem is windows username has ã in it. So it is difficult to change user folder name in windows 10. Could Barrier support this kind of character?

<!-- gh-comment-id:691322787 --> @jsantosdias commented on GitHub (Sep 11, 2020): So figured out that the problem is windows username has ã in it. So it is difficult to change user folder name in windows 10. Could Barrier support this kind of character?
Author
Owner

@DigitalFunk commented on GitHub (Sep 17, 2020):

@jsantosdias - Unfortunately many windows applications have trouble with accented characters.

After looking at it with Process Monitor it seems like Barrier is only using your username when it is looking up the path to the SSL fingerprints (in %LOCALAPPDATA%), so a possible workaround may be disabling SSL? (not recommended).

As this can happen with many other applications as well, I recommend saving yourself some trouble and changing your Windows username and user folder. It's not as hard as you might think, it should only take a couple of minutes (see video guide here)

<!-- gh-comment-id:694389192 --> @DigitalFunk commented on GitHub (Sep 17, 2020): @jsantosdias - Unfortunately many windows applications have trouble with accented characters. After looking at it with Process Monitor it seems like Barrier is only using your username when it is looking up the path to the SSL fingerprints (in %LOCALAPPDATA%), so a possible workaround may be disabling SSL? **(not recommended)**. As this can happen with many other applications as well, I recommend saving yourself some trouble and changing your Windows username and user folder. It's not as hard as you might think, it should only take a couple of minutes (see video guide [here](https://www.youtube.com/watch?v=w5N2aaiToiQ))
Author
Owner

@jsantosdias commented on GitHub (Sep 17, 2020):

Thank you, DigitalFunk! I did change the folder name, and some functions in windows started working better. Barrier works fine, now, thank you! Only had problem with Outlook, but started all and it's ok! Who could say a ~made such a difference!

<!-- gh-comment-id:694490760 --> @jsantosdias commented on GitHub (Sep 17, 2020): Thank you, DigitalFunk! I did change the folder name, and some functions in windows started working better. Barrier works fine, now, thank you! Only had problem with Outlook, but started all and it's ok! Who could say a ~made such a difference!
Author
Owner

@shymega commented on GitHub (Sep 19, 2020):

Closing, Windows doesn't support Unicode in usernames, so we can't fix this. Not our problem, sorry.

<!-- gh-comment-id:695337791 --> @shymega commented on GitHub (Sep 19, 2020): Closing, Windows doesn't support Unicode in usernames, so we can't fix this. Not our problem, sorry.
Author
Owner

@RealLordK1 commented on GitHub (Sep 19, 2020):

My username doesn't use any problematic character (LordK1).

<!-- gh-comment-id:695347809 --> @RealLordK1 commented on GitHub (Sep 19, 2020): My username doesn't use any problematic character (LordK1).
Author
Owner

@Colanth commented on GitHub (Sep 19, 2020):

'L' in Unicode would be a "probelematic character". It's the coding, as well as the character. The fact that a character is presented in Unicode makes it a 16 bit datum, not an 8 bit datum.

<!-- gh-comment-id:695350266 --> @Colanth commented on GitHub (Sep 19, 2020): 'L' in Unicode would be a "probelematic character". It's the coding, as well as the character. The fact that a character is presented in Unicode makes it a 16 bit datum, not an 8 bit datum.
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#658
No description provided.