github-starred/barrier

Fork 0

mirror of https://github.com/debauchee/barrier.git synced 2026-05-15 14:16:02 -06:00

[GH-ISSUE #2081] NixOS Stuck on barrier is starting #1504

New issue

Open

opened 2026-05-05 07:53:42 -06:00 by gitea-mirror · 5 comments

gitea-mirror commented

2026-05-05 07:53:42 -06:00

Owner

Originally created by @JackPala on GitHub (Jul 22, 2024).
Original GitHub issue: https://github.com/debauchee/barrier/issues/2081

What happened?

Stuck on Barrier is Starting Forever

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

Nixpkgs for 24.05

What OSes are you seeing the problem on? (Check all that apply)

Linux

What OS versions are you using?

NixOS 24.05

Relevant log output

No log output other than the -f --no-tray connecting message forever and `Barrier is starting`

Any other information

Stuck on Barrier is starting forever

Originally created by @JackPala on GitHub (Jul 22, 2024). Original GitHub issue: https://github.com/debauchee/barrier/issues/2081 ### What happened? Stuck on Barrier is Starting Forever ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? Nixpkgs for 24.05 ### What OSes are you seeing the problem on? (Check all that apply) Linux ### What OS versions are you using? NixOS 24.05 ### Relevant log output ```shell No log output other than the -f --no-tray connecting message forever and `Barrier is starting` ``` ### Any other information Stuck on `Barrier is starting` forever

gitea-mirror commented

2026-05-05 07:53:44 -06:00

Author

Owner

@ChiefArug commented on GitHub (Jul 27, 2024):

Is the port that barrier is set to use being used by anything else?

@ChiefArug commented on GitHub (Jul 27, 2024): Is the port that barrier is set to use being used by anything else?

gitea-mirror commented

2026-05-05 07:53:46 -06:00

Author

Owner

@JackPala commented on GitHub (Jul 27, 2024):

Is the port that barrier is set to use being used by anything else?

It's the client that's causing the issue, and no I nmapped it and it seemed fine

@JackPala commented on GitHub (Jul 27, 2024): > Is the port that barrier is set to use being used by anything else? It's the client that's causing the issue, and no I nmapped it and it seemed fine

gitea-mirror commented

2026-05-05 07:53:48 -06:00

Author

Owner

@NemoSomnium commented on GitHub (Aug 4, 2024):

Same issue for me

@NemoSomnium commented on GitHub (Aug 4, 2024): Same issue for me

gitea-mirror commented

2026-05-05 07:53:49 -06:00

Author

Owner

@NemoSomnium commented on GitHub (Aug 15, 2024):

It fixed for me, the problem was related to dns. Check barrier logs on both machines.

@NemoSomnium commented on GitHub (Aug 15, 2024): It fixed for me, the problem was related to dns. Check barrier logs on both machines.

gitea-mirror commented

2026-05-05 07:53:51 -06:00

Author

Owner

@JackPala commented on GitHub (Aug 16, 2024):

It fixed for me, the problem was related to dns. Check barrier logs on both machines.

I was using direct IP connection not hostnames, on the same subnet, however pinging by hostname works correctly both ways so I've ruled out DNS.

It appears that in this case the barrier client doesn't even send any data out as when I wiresharked my connection I didn't get any data out that would look like it would be from the barrier client. It's as if the service is either not beginning an initial start, or calling to nothing. Not sure other than that as the logs do not provide any further info other than the provided single line output saying that it is starting.

@JackPala commented on GitHub (Aug 16, 2024): > It fixed for me, the problem was related to dns. Check barrier logs on both machines. I was using direct IP connection not hostnames, on the same subnet, however pinging by hostname works correctly both ways so I've ruled out DNS. It appears that in this case the barrier client doesn't even send any data out as when I wiresharked my connection I didn't get any data out that would look like it would be from the barrier client. It's as if the service is either not beginning an initial start, or calling to nothing. Not sure other than that as the logs do not provide any further info other than the provided single line output saying that it is starting.

No labels

Rows
Columns