github-starred/barrier

Fork 0

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

[GH-ISSUE #1038] My server connects but my clients say barrier is starting. #825

New issue

Open

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

gitea-mirror commented

2026-05-05 07:11:11 -06:00

Owner

Originally created by @AustinBoath on GitHub (Jan 27, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1038

My server is a gaming PC running Windows 10, and my clients are a Macbook Air running MacOS Big Sur and a Toshiba Satellite running Ubuntu 20.10.
When I run it from my Desktop PC, the server runs just fine but the clients are not connecting.
I have auto config enabled.

When I make my Macbook the server, or my Toshiba the server, it runs fine. They are both connected on Wifi while the desktop is on ethernet (Same wifi network) with no WiFi capabilities or networking card installed.
I want to make my gaming pc the server because otherwise the delay is way too big to play games on.

Please keep in mind that I do not understand much about networking so keep it brief and easy.

Originally created by @AustinBoath on GitHub (Jan 27, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1038 My server is a gaming PC running Windows 10, and my clients are a Macbook Air running MacOS Big Sur and a Toshiba Satellite running Ubuntu 20.10. When I run it from my Desktop PC, the server runs just fine but the clients are not connecting. I have auto config enabled. When I make my Macbook the server, or my Toshiba the server, it runs fine. They are both connected on Wifi while the desktop is on ethernet (Same wifi network) with no WiFi capabilities or networking card installed. I want to make my gaming pc the server because otherwise the delay is way too big to play games on. Please keep in mind that I do not understand much about networking so keep it brief and easy.

gitea-mirror commented

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

Author

Owner

@ravendward commented on GitHub (Jan 27, 2021):

Having the exact same issue, gonna follow this for if you find help. I've tried opening the ports on my Gaming PC, no dice.

@ravendward commented on GitHub (Jan 27, 2021): Having the exact same issue, gonna follow this for if you find help. I've tried opening the ports on my Gaming PC, no dice.

gitea-mirror commented

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

Author

Owner

@nickescobedo commented on GitHub (Jan 27, 2021):

Check the logs from Barrier both on the client and server. Usually it will give you reasons why stuff is happening.

@nickescobedo commented on GitHub (Jan 27, 2021): Check the logs from Barrier both on the client and server. Usually it will give you reasons why stuff is happening.

gitea-mirror commented

2026-05-05 07:11:17 -06:00

Author

Owner

@ravendward commented on GitHub (Jan 28, 2021):

Hey Nick, thanks.

"WARNING: failed to connect to server: connection refused"

I've opened up the ports on both my client and server.

@ravendward commented on GitHub (Jan 28, 2021): Hey Nick, thanks. "WARNING: failed to connect to server: connection refused" I've opened up the ports on both my client and server.

gitea-mirror commented

2026-05-05 07:11:18 -06:00

Author

Owner

@geoelectric commented on GitHub (Feb 3, 2021):

I ran into this problem connecting to a Catalina server from the Ubuntu 20.04 snap. The auto-config checkbox is being ignored entirely, and whatever is in the box is being supplied as the server. In the default case, that's blank.

Main symptom is client stuck on starting, with a log spam of

[2021-02-03T14:29:18] NOTE: connecting to '': :::24800
[2021-02-03T14:29:18] INFO: OpenSSL 1.1.1  11 Sep 2018
[2021-02-03T14:29:18] WARNING: failed to connect to server: Connection refused

Can validate the checkbox is being ignored by unchecking auto-config, supplying a string like "placeholder", then re-checking. You'll see placeholder in the logs as the server address even though auto-config is checked.

Catalina version: 10.15.7, Barrier: 2.3.3-release-3395cca9 (installed from Homebrew)
Ubuntu version: 20.04.1 LTS, Barrier: 2.3.3-release-bbd1accb (installed from Snap)

@geoelectric commented on GitHub (Feb 3, 2021): I ran into this problem connecting to a Catalina server from the Ubuntu 20.04 snap. The auto-config checkbox is being ignored entirely, and whatever is in the box is being supplied as the server. In the default case, that's blank. Main symptom is client stuck on starting, with a log spam of ``` [2021-02-03T14:29:18] NOTE: connecting to '': :::24800 [2021-02-03T14:29:18] INFO: OpenSSL 1.1.1 11 Sep 2018 [2021-02-03T14:29:18] WARNING: failed to connect to server: Connection refused ``` Can validate the checkbox is being ignored by unchecking auto-config, supplying a string like "placeholder", then re-checking. You'll see placeholder in the logs as the server address even though auto-config is checked. Catalina version: 10.15.7, Barrier: 2.3.3-release-3395cca9 (installed from Homebrew) Ubuntu version: 20.04.1 LTS, Barrier: 2.3.3-release-bbd1accb (installed from Snap)

gitea-mirror commented

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

Author

Owner

@geoelectric commented on GitHub (Feb 3, 2021):

I just uninstalled the snap version from the client and tried the apt version instead. That installed 2.3.2-Release-00000000. That client auto-configured correctly.

I have no idea if it was the difference in version, or the uninstall/reinstall. Reinstalled version went through a first user experience and had no server set, so either didn't find or didn't use an old config.

@geoelectric commented on GitHub (Feb 3, 2021): I just uninstalled the snap version from the client and tried the apt version instead. That installed 2.3.2-Release-00000000. That client auto-configured correctly. I have no idea if it was the difference in version, or the uninstall/reinstall. Reinstalled version went through a first user experience and had no server set, so either didn't find or didn't use an old config.

No labels

Rows
Columns