github-starred/barrier

Fork 0

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

[GH-ISSUE #1782] failed to connect to server: No route to host #1310

New issue

Open

opened 2026-05-05 07:43:01 -06:00 by gitea-mirror · 7 comments

gitea-mirror commented

2026-05-05 07:43:01 -06:00

Owner

Originally created by @manjukb004 on GitHub (Sep 19, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1782

What happened?

struck starting up

Version

v2.4.0

Git commit hash (if applicable)

No response

If applicable, where did you install Barrier from?

using apt

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

Linux

What OS versions are you using?

PRETTY_NAME="Ubuntu 22.04 LTS"
NAME="Ubuntu"
VERSION_ID="22.04"
VERSION="22.04 LTS (Jammy Jellyfish)"
VERSION_CODENAME=jammy
ID=ubuntu
ID_LIKE=debian
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
UBUNTU_CODENAME=jammy

Relevant log output

[2022-09-19T04:17:15] WARNING: failed to connect to server: No route to host
[2022-09-19T04:17:16] NOTE: connecting to '198.168.0.107': 198.168.0.107:24800
[2022-09-19T04:17:16] DEBUG: Opening new socket: 00C3CCB0
[2022-09-19T04:17:16] INFO: OpenSSL 3.0.2 15 Mar 2022
[2022-09-19T04:17:18] DEBUG: Closing socket: 00C3CCB0
[2022-09-19T04:17:18] DEBUG: retry in 1 seconds
[2022-09-19T04:17:18] WARNING: failed to connect to server:

Any other information

this was working before

Originally created by @manjukb004 on GitHub (Sep 19, 2022). Original GitHub issue: https://github.com/debauchee/barrier/issues/1782 ### What happened? struck starting up ![Screenshot from 2022-09-19 04-24-02](https://user-images.githubusercontent.com/113873236/190944986-785b2343-ec37-4167-ab09-286ee0f06a86.png) ### Version v2.4.0 ### Git commit hash (if applicable) _No response_ ### If applicable, where did you install Barrier from? using apt ### What OSes are you seeing the problem on? (Check all that apply) Linux ### What OS versions are you using? PRETTY_NAME="Ubuntu 22.04 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/" SUPPORT_URL="https://help.ubuntu.com/" BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/" PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy" UBUNTU_CODENAME=jammy ### Relevant log output ```shell [2022-09-19T04:17:15] WARNING: failed to connect to server: No route to host [2022-09-19T04:17:16] NOTE: connecting to '198.168.0.107': 198.168.0.107:24800 [2022-09-19T04:17:16] DEBUG: Opening new socket: 00C3CCB0 [2022-09-19T04:17:16] INFO: OpenSSL 3.0.2 15 Mar 2022 [2022-09-19T04:17:18] DEBUG: Closing socket: 00C3CCB0 [2022-09-19T04:17:18] DEBUG: retry in 1 seconds [2022-09-19T04:17:18] WARNING: failed to connect to server: ``` ### Any other information this was working before

gitea-mirror commented

2026-05-05 07:43:05 -06:00

Author

Owner

@StevenPartridge commented on GitHub (Aug 10, 2023):

I have this exact issue. Server is Garuda Linux, Client is Pop_OS, the issue started after updating Pop_OS. I'll post more information if I can figure out what updated to break functionality

@StevenPartridge commented on GitHub (Aug 10, 2023): I have this exact issue. Server is Garuda Linux, Client is Pop_OS, the issue started after updating Pop_OS. I'll post more information if I can figure out what updated to break functionality

gitea-mirror commented

2026-05-05 07:43:07 -06:00

Author

Owner

@HiddenBit-X commented on GitHub (Oct 17, 2024):

I have 2 Mac's connected a 2013 Pro and Client is Mac 2018 Mac mini, this was also working and suddenly stopped working and the log on the client now shows this all the time: WARNING: failed to connect to server '192.168.0.xxx': cannot connect socket: no route to host.

It is perfectly pinging each other and all other aspects of the two is working just fine.
I think I have tried almost anything disable ssl and so on so fort. nothing seems to help.

The server also see an entry for the client although the client seems to think it has these errors, I have tried to reinstall client with no luck.

Any ideas on this?

@HiddenBit-X commented on GitHub (Oct 17, 2024): I have 2 Mac's connected a 2013 Pro and Client is Mac 2018 Mac mini, this was also working and suddenly stopped working and the log on the client now shows this all the time: WARNING: failed to connect to server '192.168.0.xxx': cannot connect socket: no route to host. It is perfectly pinging each other and all other aspects of the two is working just fine. I think I have tried almost anything disable ssl and so on so fort. nothing seems to help. The server also see an entry for the client although the client seems to think it has these errors, I have tried to reinstall client with no luck. Any ideas on this?

gitea-mirror commented

2026-05-05 07:43:09 -06:00

Author

Owner

@HiddenBit-X commented on GitHub (Oct 17, 2024):

I did a lot of trail and error on this, I could not change my screen name found this, seems like it got back after changing name

It still kind of fails when I reboot the client, I will see here later on, pretty weird how this acts.

I was able to get the new name to take effect by rebooting my MacBook after removing the /Users//Library/Preferences/com.github.Barrier.plist file.

@HiddenBit-X commented on GitHub (Oct 17, 2024): I did a lot of trail and error on this, I could not change my screen name found this, seems like it got back after changing name It still kind of fails when I reboot the client, I will see here later on, pretty weird how this acts. I was able to get the new name to take effect by rebooting my MacBook after removing the /Users/<username>/Library/Preferences/com.github.Barrier.plist file.

gitea-mirror commented

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

Author

Owner

@enter-dragon commented on GitHub (Dec 24, 2024):

I had this problem on Mac after update. MacOS had revoke LAN access to Barrier. Given access after reboot and could connect again.

@enter-dragon commented on GitHub (Dec 24, 2024): I had this problem on Mac after update. MacOS had revoke LAN access to Barrier. Given access after reboot and could connect again.

gitea-mirror commented

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

Author

Owner

@DeepYogurt commented on GitHub (Jan 2, 2025):

Hi enter-dragon -- how exactly did you tell that access had been denied and how exactly did you give it back?? Thanks...

This is really weird for me - this "no route to host" happens for a while and then is OK for a while and then fails for a while - can't figure out why/how it's happening or why it keeps changing - so weird.

Thanks for any ideas...

-bob

@DeepYogurt commented on GitHub (Jan 2, 2025): Hi enter-dragon -- how exactly did you tell that access had been denied and how exactly did you give it back?? Thanks... This is really weird for me - this "no route to host" happens for a while and then is OK for a while and then fails for a while - can't figure out why/how it's happening or why it keeps changing - so weird. Thanks for any ideas... -bob

gitea-mirror commented

2026-05-05 07:43:15 -06:00

Author

Owner

@PavulonTwist commented on GitHub (Jan 3, 2025):

I had this problem on Mac after update. MacOS had revoke LAN access to Barrier. Given access after reboot and could connect again.

Thank you very much! It was also the case for me even though MacOS settings were suggesting that the application has LAN access.

I have found these settings in Apple -> System Settings... -> Privacy & Security -> Local Network.
There Barrier was toggled to have the access. I have toggled it off and on and that made it working again.

@PavulonTwist commented on GitHub (Jan 3, 2025): > I had this problem on Mac after update. MacOS had revoke LAN access to Barrier. Given access after reboot and could connect again. Thank you very much! It was also the case for me even though MacOS settings were suggesting that the application has LAN access. I have found these settings in `Apple` -> `System Settings...` -> `Privacy & Security` -> `Local Network`. There `Barrier` was toggled to have the access. I have toggled it off and on and that made it working again.

gitea-mirror commented

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

Author

Owner

@rafaelpoa commented on GitHub (Jan 8, 2025):

I had this problem on Mac after update. MacOS had revoke LAN access to Barrier. Given access after reboot and could connect again.

Thank you very much! It was also the case for me even though MacOS settings were suggesting that the application has LAN access.

I have found these settings in Apple -> System Settings... -> Privacy & Security -> Local Network. There Barrier was toggled to have the access. I have toggled it off and on and that made it working again.

I had exactly the same problem. After simply going into the local network and disabling and enabling it, it started working again. I hope I don't have to do this every time. Thanks

@rafaelpoa commented on GitHub (Jan 8, 2025): > > I had this problem on Mac after update. MacOS had revoke LAN access to Barrier. Given access after reboot and could connect again. > > Thank you very much! It was also the case for me even though MacOS settings were suggesting that the application has LAN access. > > I have found these settings in `Apple` -> `System Settings...` -> `Privacy & Security` -> `Local Network`. There `Barrier` was toggled to have the access. I have toggled it off and on and that made it working again. I had exactly the same problem. After simply going into the local network and disabling and enabling it, it started working again. I hope I don't have to do this every time. Thanks

No labels

Rows
Columns