[GH-ISSUE #922] Windows: Unable to open trustedServersFilename #735

Open
opened 2026-05-05 07:00:18 -06:00 by gitea-mirror · 10 comments
Owner

Originally created by @apexJCL on GitHub (Oct 20, 2020).
Original GitHub issue: https://github.com/debauchee/barrier/issues/922

Describe the bug
Barrier cannot connect to Linux's server, on the logs it shows it cannot open the trustedServers.txt file and its showing a path to the file with forward slashes.

To Reproduce

Steps to reproduce the behavior:

  1. Run Barrier as a client on Windows
  2. Connect to a server (I haven't tested with a Windows server)

Expected behavior
Connection is successful

Screenshots
None

Desktop (please complete the following information):

  • OS: Windows 10 (build 19041.572)
  • Barrier version: 2.3.3-release-3395cca9

Additional context

Logs (redacted):

[2020-10-20T11:07:38] NOTE: connecting to '192.168.1.82': 192.168.1.82:24800
[2020-10-20T11:07:38] INFO: OpenSSL 1.0.2l  25 May 2017
[2020-10-20T11:07:38] NOTE: server fingerprint: [redacted]
[2020-10-20T11:07:38] NOTE: trustedServersFilename: C:\Users\José Carlos\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-20T11:07:38] NOTE: Unable to open trustedServersFile: C:\Users\José Carlos\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-20T11:07:38] ERROR: failed to verify server certificate fingerprint
[2020-10-20T11:07:49] INFO: service command updated
[2020-10-20T11:07:50] INFO: process started but command is empty, shutting down
[2020-10-20T11:07:50] INFO: got ipc shutdown message
[2020-10-20T11:07:50] NOTE: stopped client
[2020-10-20T11:07:51] INFO: process 4324 was shutdown gracefully

Update

Updated logs to reflect my username's folder name, a current test with a new windows account with a username that does not uses special characters/spaces seemed to fix this issue.

Originally created by @apexJCL on GitHub (Oct 20, 2020). Original GitHub issue: https://github.com/debauchee/barrier/issues/922 **Describe the bug** Barrier cannot connect to Linux's server, on the logs it shows it cannot open the `trustedServers.txt` file and its showing a path to the file with forward slashes. **To Reproduce** Steps to reproduce the behavior: 1. Run Barrier as a client on Windows 2. Connect to a server (I haven't tested with a Windows server) **Expected behavior** Connection is successful **Screenshots** None **Desktop (please complete the following information):** - OS: Windows 10 (build 19041.572) - Barrier version: 2.3.3-release-3395cca9 **Additional context** Logs (redacted): ``` [2020-10-20T11:07:38] NOTE: connecting to '192.168.1.82': 192.168.1.82:24800 [2020-10-20T11:07:38] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-10-20T11:07:38] NOTE: server fingerprint: [redacted] [2020-10-20T11:07:38] NOTE: trustedServersFilename: C:\Users\José Carlos\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt [2020-10-20T11:07:38] NOTE: Unable to open trustedServersFile: C:\Users\José Carlos\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt [2020-10-20T11:07:38] ERROR: failed to verify server certificate fingerprint [2020-10-20T11:07:49] INFO: service command updated [2020-10-20T11:07:50] INFO: process started but command is empty, shutting down [2020-10-20T11:07:50] INFO: got ipc shutdown message [2020-10-20T11:07:50] NOTE: stopped client [2020-10-20T11:07:51] INFO: process 4324 was shutdown gracefully ``` --- **Update** Updated logs to reflect my username's folder name, a current test with a new windows account with a username that does not uses special characters/spaces seemed to fix this issue.
Author
Owner

@kiemlicz commented on GitHub (Oct 28, 2020):

Having similar issue, difference is that my windows client loops forever and prints the remote fingerprint

2020-10-28T07:18:07] WARNING: failed to connect to server: Timed out
[2020-10-28T07:18:08] NOTE: connecting to '192.168.8.170': 192.168.8.170:24800
[2020-10-28T07:18:08] INFO: OpenSSL 1.0.2l  25 May 2017
[2020-10-28T07:18:08] NOTE: server fingerprint: 4D:0F:47:CA:BB:90:4C:57:CD:83:58:17:57:B2:B2:42:E5:92:06:76
[2020-10-28T07:18:08] NOTE: trustedServersFilename: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-28T07:18:08] NOTE: Unable to open trustedServersFile: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-28T07:18:08] ERROR: failed to verify server certificate f
ingerprint
[
2020-10-28T07:18:23] WARNING: failed to connect to server: Timed out
[2020-10-28T07:18:24] NOTE: connecting to '192.168.8.170': 192.168.8.170:24800
[2020-10-28T07:18:24] INFO: OpenSSL 1.0.2l  25 May 2017
[2020-10-28T07:18:24] NOTE: server fingerprint: 4D:0F:47:CA:BB:90:4C:57:CD:83:58:17:57:B2:B2:42:E5:92:06:76
[2020-10-28T07:18:24] NOTE: trustedServersFilename: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-28T07:18:24] NOTE: Unable to open trustedServersFile: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-28T07:18:24] ERROR: failed to verify server certificat
e fingerprint
<!-- gh-comment-id:717775896 --> @kiemlicz commented on GitHub (Oct 28, 2020): Having similar issue, difference is that my windows client loops forever and prints the remote fingerprint ``` 2020-10-28T07:18:07] WARNING: failed to connect to server: Timed out [2020-10-28T07:18:08] NOTE: connecting to '192.168.8.170': 192.168.8.170:24800 [2020-10-28T07:18:08] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-10-28T07:18:08] NOTE: server fingerprint: 4D:0F:47:CA:BB:90:4C:57:CD:83:58:17:57:B2:B2:42:E5:92:06:76 [2020-10-28T07:18:08] NOTE: trustedServersFilename: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt [2020-10-28T07:18:08] NOTE: Unable to open trustedServersFile: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt [2020-10-28T07:18:08] ERROR: failed to verify server certificate f ingerprint [ 2020-10-28T07:18:23] WARNING: failed to connect to server: Timed out [2020-10-28T07:18:24] NOTE: connecting to '192.168.8.170': 192.168.8.170:24800 [2020-10-28T07:18:24] INFO: OpenSSL 1.0.2l 25 May 2017 [2020-10-28T07:18:24] NOTE: server fingerprint: 4D:0F:47:CA:BB:90:4C:57:CD:83:58:17:57:B2:B2:42:E5:92:06:76 [2020-10-28T07:18:24] NOTE: trustedServersFilename: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt [2020-10-28T07:18:24] NOTE: Unable to open trustedServersFile: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt [2020-10-28T07:18:24] ERROR: failed to verify server certificat e fingerprint ```
Author
Owner

@apexJCL commented on GitHub (Oct 28, 2020):

I've tested with a new windows account and it seems that special
characters/spaces aren't escaped properly.

Create a new account without special characters/spaces, it will work (at
least it did for me)

On Wed, 28 Oct 2020, 1:22 am stachu, notifications@github.com wrote:

Having similar issue, difference is that my windows client loops forever
and prints the remote fingerprint

2020-10-28T07:18:07] WARNING: failed to connect to server: Timed out
[2020-10-28T07:18:08] NOTE: connecting to '192.168.8.170': 192.168.8.170:24800
[2020-10-28T07:18:08] INFO: OpenSSL 1.0.2l 25 May 2017
[2020-10-28T07:18:08] NOTE: server fingerprint: 4D:0F:47:CA:BB:90:4C:57:CD:83:58:17:57:B2:B2:42:E5:92:06:76
[2020-10-28T07:18:08] NOTE: trustedServersFilename: C:\Users<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-28T07:18:08] NOTE: Unable to open trustedServersFile: C:\Users<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-28T07:18:08] ERROR: failed to verify server certificate f
ingerprint
[
2020-10-28T07:18:23] WARNING: failed to connect to server: Timed out
[2020-10-28T07:18:24] NOTE: connecting to '192.168.8.170': 192.168.8.170:24800
[2020-10-28T07:18:24] INFO: OpenSSL 1.0.2l 25 May 2017
[2020-10-28T07:18:24] NOTE: server fingerprint: 4D:0F:47:CA:BB:90:4C:57:CD:83:58:17:57:B2:B2:42:E5:92:06:76
[2020-10-28T07:18:24] NOTE: trustedServersFilename: C:\Users<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-28T07:18:24] NOTE: Unable to open trustedServersFile: C:\Users<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt
[2020-10-28T07:18:24] ERROR: failed to verify server certificat
e fingerprint


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/debauchee/barrier/issues/922#issuecomment-717775896,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA6ZYAELEDPHKVCWTGQU36LSM7IFPANCNFSM4SYWQDPA
.

<!-- gh-comment-id:717951175 --> @apexJCL commented on GitHub (Oct 28, 2020): I've tested with a new windows account and it seems that special characters/spaces aren't escaped properly. Create a new account without special characters/spaces, it will work (at least it did for me) On Wed, 28 Oct 2020, 1:22 am stachu, <notifications@github.com> wrote: > Having similar issue, difference is that my windows client loops forever > and prints the remote fingerprint > > 2020-10-28T07:18:07] WARNING: failed to connect to server: Timed out > [2020-10-28T07:18:08] NOTE: connecting to '192.168.8.170': 192.168.8.170:24800 > [2020-10-28T07:18:08] INFO: OpenSSL 1.0.2l 25 May 2017 > [2020-10-28T07:18:08] NOTE: server fingerprint: 4D:0F:47:CA:BB:90:4C:57:CD:83:58:17:57:B2:B2:42:E5:92:06:76 > [2020-10-28T07:18:08] NOTE: trustedServersFilename: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt > [2020-10-28T07:18:08] NOTE: Unable to open trustedServersFile: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt > [2020-10-28T07:18:08] ERROR: failed to verify server certificate f > ingerprint > [ > 2020-10-28T07:18:23] WARNING: failed to connect to server: Timed out > [2020-10-28T07:18:24] NOTE: connecting to '192.168.8.170': 192.168.8.170:24800 > [2020-10-28T07:18:24] INFO: OpenSSL 1.0.2l 25 May 2017 > [2020-10-28T07:18:24] NOTE: server fingerprint: 4D:0F:47:CA:BB:90:4C:57:CD:83:58:17:57:B2:B2:42:E5:92:06:76 > [2020-10-28T07:18:24] NOTE: trustedServersFilename: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt > [2020-10-28T07:18:24] NOTE: Unable to open trustedServersFile: C:\Users\<EDIT>\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt > [2020-10-28T07:18:24] ERROR: failed to verify server certificat > e fingerprint > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <https://github.com/debauchee/barrier/issues/922#issuecomment-717775896>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AA6ZYAELEDPHKVCWTGQU36LSM7IFPANCNFSM4SYWQDPA> > . >
Author
Owner

@kiemlicz commented on GitHub (Oct 28, 2020):

Thanks
Possibly this is the case, I don't have the luxury to test this

<!-- gh-comment-id:717970222 --> @kiemlicz commented on GitHub (Oct 28, 2020): Thanks Possibly this is the case, I don't have the luxury to test this
Author
Owner

@ZaitsevY commented on GitHub (Nov 2, 2020):

I'm facing the same problem because Windows account name is in Cyrillic.
NOTE: Unable to open trustedServersFile: C:\Users\Юрий\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt

<!-- gh-comment-id:720410729 --> @ZaitsevY commented on GitHub (Nov 2, 2020): I'm facing the same problem because Windows account name is in Cyrillic. `NOTE: Unable to open trustedServersFile: C:\Users\Юрий\AppData\Local\Barrier/SSL/Fingerprints/TrustedServers.txt`
Author
Owner

@benawi1402 commented on GitHub (Nov 13, 2020):

I'm having the same issue with a german "ß" in my Windows account name.

<!-- gh-comment-id:726699967 --> @benawi1402 commented on GitHub (Nov 13, 2020): I'm having the same issue with a german "ß" in my Windows account name.
Author
Owner

@helieldm commented on GitHub (Dec 5, 2020):

Same with an "é" in my name. Seems like a simple bug to fix ?

<!-- gh-comment-id:739329125 --> @helieldm commented on GitHub (Dec 5, 2020): Same with an "é" in my name. Seems like a simple bug to fix ?
Author
Owner

@ghost commented on GitHub (Feb 7, 2021):

+1 same issue with č, š, and ž characters. IMO SSL path should be configurable (even if only through editing the .sgc file) to at least offer a work-around.

<!-- gh-comment-id:774673573 --> @ghost commented on GitHub (Feb 7, 2021): +1 same issue with `č`, `š`, and `ž` characters. IMO SSL path should be configurable (even if only through editing the .sgc file) to at least offer a work-around.
Author
Owner

@pousterlus commented on GitHub (Feb 8, 2021):

+1, same here, "é" in Windows account name :)

<!-- gh-comment-id:775351964 --> @pousterlus commented on GitHub (Feb 8, 2021): +1, same here, "é" in Windows account name :)
Author
Owner

@sintoris commented on GitHub (Apr 23, 2021):

Same issue with Greek letters in the account name

<!-- gh-comment-id:825497942 --> @sintoris commented on GitHub (Apr 23, 2021): Same issue with Greek letters in the account name
Author
Owner

@ZaitsevY commented on GitHub (Aug 20, 2021):

Workaround here: disable SLL support in both server and client (UI, Barrier -> Change Settings -> Enable SSL - uncheck it). Use with caution, this networking is less secure.

<!-- gh-comment-id:902727108 --> @ZaitsevY commented on GitHub (Aug 20, 2021): Workaround here: disable SLL support in both server and client (UI, Barrier -> Change Settings -> Enable SSL - uncheck it). Use with caution, this networking is less secure.
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#735
No description provided.