[GH-ISSUE #518] SNAP: Running barrierc from CLI doesn't read TrustedServers.txt file? #405

New issue

Closed

opened 2026-05-05 06:18:08 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

2026-05-05 06:18:08 -06:00

Owner

Originally created by @firrae on GitHub (Dec 3, 2019).
Original GitHub issue: https://github.com/debauchee/barrier/issues/518

Operating Systems

Server: Microsoft Windows 10 1903 (OS Build 18362.476)

Client: Ubuntu 18.04

Barrier Version

Server: 2.3.2 Snapshot 210c2b70

Client 2.3.2 Snapshot 13ac2482

Steps to reproduce bug

Run server on Windows (SSL on, auto startup)
Run CLI command: /snap/barrier/109/usr/bin/barrierc -f --debug WARNING --name Steve-Workstation --enable-crypto [192.168.2.7]:24800
See:

ERROR: failed to verify server certificate fingerprint
WARNING: failed to connect to server: Timed out
...

Other info

The TrustedServers.txt file in the SNAP folder for the version has my server's key in it from using the GUI.

When did the problem start to occur? I was trying to create an auto start script to get the client going when the machine starts up, testing it in the CLI produces this. Using the GUI everything works fine, but I'm not sure how to get that to auto start.
Is there a way to work around it? Use GUI, but I can't figure out how to automate that.
Does this bug prevent you from using Barrier entirely? Not really, but it is annoying and I'd like to sort it out.

Originally created by @firrae on GitHub (Dec 3, 2019). Original GitHub issue: https://github.com/debauchee/barrier/issues/518 ### Operating Systems ### Server: Microsoft Windows 10 1903 (OS Build 18362.476) Client: Ubuntu 18.04 ### Barrier Version ### Server: 2.3.2 Snapshot 210c2b70 Client 2.3.2 Snapshot 13ac2482 ### Steps to reproduce bug ### 1. Run server on Windows (SSL on, auto startup) 2. Run CLI command: `/snap/barrier/109/usr/bin/barrierc -f --debug WARNING --name Steve-Workstation --enable-crypto [192.168.2.7]:24800` 3. See: ``` ERROR: failed to verify server certificate fingerprint WARNING: failed to connect to server: Timed out ... ``` ### Other info ### The TrustedServers.txt file in the SNAP folder for the version has my server's key in it from using the GUI. * When did the problem start to occur? I was trying to create an auto start script to get the client going when the machine starts up, testing it in the CLI produces this. Using the GUI everything works fine, but I'm not sure how to get that to auto start. * Is there a way to work around it? Use GUI, but I can't figure out how to automate that. * Does this bug prevent you from using Barrier entirely? Not really, but it is annoying and I'd like to sort it out.

gitea-mirror closed this issue

2026-05-05 06:18:10 -06:00

gitea-mirror commented

2026-05-05 06:18:12 -06:00

Author

Owner

@maxiberta commented on GitHub (Dec 3, 2019):

Fwiw, I'm able to run the snapped barrierc on login with no issues (2.3.2-24-g13ac2482 snap, Ubuntu 18.04), with this autostart script. Hope it helps.

$ cat ~/.config/autostart/barrier.desktop
[Desktop Entry]
Type=Application
Exec=run-one-constantly /snap/bin/barrierc -f --no-tray --debug ERROR --name client --enable-crypto server
Hidden=false
NoDisplay=false
X-GNOME-Autostart-enabled=true
Name=Barrier
Comment=

@maxiberta commented on GitHub (Dec 3, 2019): Fwiw, I'm able to run the snapped `barrierc` on login with no issues (2.3.2-24-g13ac2482 snap, Ubuntu 18.04), with this autostart script. Hope it helps. ``` $ cat ~/.config/autostart/barrier.desktop [Desktop Entry] Type=Application Exec=run-one-constantly /snap/bin/barrierc -f --no-tray --debug ERROR --name client --enable-crypto server Hidden=false NoDisplay=false X-GNOME-Autostart-enabled=true Name=Barrier Comment= ```

gitea-mirror commented

2026-05-05 06:18:14 -06:00

Author

Owner

@firrae commented on GitHub (Jan 1, 2020):

That worked for me @maxiberta! Thanks for sharing!

@firrae commented on GitHub (Jan 1, 2020): That worked for me @maxiberta! Thanks for sharing!

gitea-mirror referenced this issue

2026-05-05 07:57:58 -06:00

[PR #405] [MERGED] Tidy up and fix lint errors in build scripts #1624