github-starred/barrier

Fork 0

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

[GH-ISSUE #1121] Ubuntu Client error: No route to host #898

New issue

Open

opened 2026-05-05 07:15:24 -06:00 by gitea-mirror · 6 comments

gitea-mirror commented

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

Owner

Originally created by @tienloc1 on GitHub (Apr 8, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1121

It's working fine for me yesterday but it's stopped now.

Server: Windows 10 - Server IP: 192.168.1.6
Firewall - Inbound: Added port 24800 - Done

[2021-04-08T09:47:09] INFO: starting server
[2021-04-08T09:47:09] INFO: config file: C:/Users/Loc/AppData/Local/Temp/Barrier.APCXXT
[2021-04-08T09:47:09] INFO: log level: INFO
[2021-04-08T09:47:09] INFO: service command updated
[2021-04-08T09:47:09] INFO: starting new process as privileged user
[2021-04-08T09:47:09] ERROR: failed to get desktop path, no drop target available, error=2
started server (IPv4/IPv6), waiting for clients
server status: active

Test-NetConnection result:

ComputerName   : 192.168.1.6
RemoteAddress    : 192.168.1.6
RemotePort       : 24800
InterfaceAlias   : Ethernet
SourceAddress    : 192.168.1.6
TcpTestSucceeded : True

Client: Ubuntu 20.04 - Client IP: 192.1.68.1.5

[2021-04-08T09:47:49] INFO: starting client
[2021-04-08T09:47:49] INFO: config file: /tmp/Barrier.Gkkruu
[2021-04-08T09:47:49] INFO: log level: INFO
[2021-04-08T09:47:49] NOTE: started client
[2021-04-08T09:47:49] NOTE: connecting to '192.168.1.6': 192.168.1.6:24800
[2021-04-08T09:47:49] INFO: OpenSSL 1.1.1f  31 Mar 2020
[2021-04-08T09:47:52] WARNING: failed to connect to server: No route to host

I'm not sure what happened and how I can resolve it now :(.

Originally created by @tienloc1 on GitHub (Apr 8, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1121 It's working fine for me yesterday but it's stopped now. Server: Windows 10 - Server IP: 192.168.1.6 Firewall - Inbound: Added port 24800 - Done ```html [2021-04-08T09:47:09] INFO: starting server [2021-04-08T09:47:09] INFO: config file: C:/Users/Loc/AppData/Local/Temp/Barrier.APCXXT [2021-04-08T09:47:09] INFO: log level: INFO [2021-04-08T09:47:09] INFO: service command updated [2021-04-08T09:47:09] INFO: starting new process as privileged user [2021-04-08T09:47:09] ERROR: failed to get desktop path, no drop target available, error=2 started server (IPv4/IPv6), waiting for clients server status: active ``` Test-NetConnection result: ```html ComputerName : 192.168.1.6 RemoteAddress : 192.168.1.6 RemotePort : 24800 InterfaceAlias : Ethernet SourceAddress : 192.168.1.6 TcpTestSucceeded : True ``` Client: Ubuntu 20.04 - Client IP: 192.1.68.1.5 ```html [2021-04-08T09:47:49] INFO: starting client [2021-04-08T09:47:49] INFO: config file: /tmp/Barrier.Gkkruu [2021-04-08T09:47:49] INFO: log level: INFO [2021-04-08T09:47:49] NOTE: started client [2021-04-08T09:47:49] NOTE: connecting to '192.168.1.6': 192.168.1.6:24800 [2021-04-08T09:47:49] INFO: OpenSSL 1.1.1f 31 Mar 2020 [2021-04-08T09:47:52] WARNING: failed to connect to server: No route to host ``` I'm not sure what happened and how I can resolve it now :(.

gitea-mirror commented

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

Author

Owner

@tienloc1 commented on GitHub (Apr 8, 2021):

It's working again now, but the server IP changed 192.168.1.6 to 192.168.1.3, I'm not sure why the problem resolved by itself but seems it's related to the server IP.

@tienloc1 commented on GitHub (Apr 8, 2021): It's working again now, but the server IP changed 192.168.1.6 to 192.168.1.3, I'm not sure why the problem resolved by itself but seems it's related to the server IP.

gitea-mirror commented

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

Author

Owner

@tienloc1 commented on GitHub (Apr 13, 2021):

The problem repeated again many times :(

@tienloc1 commented on GitHub (Apr 13, 2021): The problem repeated again many times :(

gitea-mirror commented

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

Author

Owner

@stonespheres commented on GitHub (Apr 14, 2021):

The problem repeated again many times :(

Are you using DHCP?

It's working again now, but the server IP changed 192.168.1.6 to 192.168.1.3, I'm not sure why the problem resolved by itself but seems it's related to the server IP.

I suspect you're getting a new lease from your router to your server, which requires you to change the server IP address in Barrier.

You can check your IP with:

ip r

EDIT: - I've just seen the server is Windows 10, these commands are for Ubuntu.
I'll leave them up as they may help you determine how to solve the issue on a Windows system.

You may also be able to specify the host name in Barrier, but I'm not 100% sure about this. To find the hostname of your server:

hostname

If you determine that it is DHCP causing the issue, or you just figure you need to work out a solution concerning changing IP addresses, may I suggest a script that grabs the servers IP address, starts Barrier on the server, then ssh a remote command to the client with the server details to start Barrier on the client. For example, I have setup:

ssh user@clientComputer '/usr/bin/barrierc -f --no-tray --debug INFO --name clientComputer --enable-crypto [IPADDRESSOFCLIENT]:PORT'

@stonespheres commented on GitHub (Apr 14, 2021): > The problem repeated again many times :( Are you using DHCP? > It's working again now, but the server IP changed 192.168.1.6 to 192.168.1.3, I'm not sure why the problem resolved by itself but seems it's related to the server IP. I suspect you're getting a new lease from your router to your server, which requires you to change the server IP address in Barrier. You can check your IP with: ``` ip r ``` **EDIT: - I've just seen the server is Windows 10, these commands are for _Ubuntu_. I'll leave them up as they may help you determine how to solve the issue on a Windows system.** You may also be able to specify the host name in Barrier, but I'm not 100% sure about this. To find the hostname of your server: ``` hostname ``` If you determine that it is DHCP causing the issue, or you just figure you need to work out a solution concerning changing IP addresses, may I suggest a script that grabs the servers IP address, starts Barrier on the server, then ssh a remote command to the client with the server details to start Barrier on the client. For example, I have setup: ``` ssh user@clientComputer '/usr/bin/barrierc -f --no-tray --debug INFO --name clientComputer --enable-crypto [IPADDRESSOFCLIENT]:PORT' ```

gitea-mirror commented

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

Author

Owner

@ERasnier commented on GitHub (Apr 16, 2021):

Yeah the client connects with the server ip entered and nothing else. You'd have to re-enter the new server ip every time the server resets.

@ERasnier commented on GitHub (Apr 16, 2021): Yeah the client connects with the server ip entered and nothing else. You'd have to re-enter the new server ip every time the server resets.

gitea-mirror commented

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

Author

Owner

@stonespheres commented on GitHub (Apr 16, 2021):

Yeah the client connects with the server ip entered and nothing else. You'd have to re-enter the new server IP every time the server resets.

It's possible to start the client instance from the server, it may help with your situation until you can assign your server a static IP address. The easiest way to do this is with ssh
Regarding the constantly changing server address: you most likely will be to be able to assign a static IP to your server from your router if it's causing you issues.

@stonespheres commented on GitHub (Apr 16, 2021): > Yeah the client connects with the server ip entered and nothing else. You'd have to re-enter the new server IP every time the server resets. It's possible to start the client instance from the server, it may help with your situation until you can assign your server a static IP address. The easiest way to do this is with `ssh` Regarding the constantly changing server address: you most likely will be to be able to assign a static IP to your server from your router if it's causing you issues.

gitea-mirror commented

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

Author

Owner

@ERasnier commented on GitHub (Apr 16, 2021):

I'm getting a refused connection from the ssh command but on the server logs it's saying that client connection has been accepted. The server logs endlessly repeats the idea that two client connections has been accepted but disconnects.

EDIT: Fixed. This it works completely now but a note that installing through snap is in a different directory than normal and a file called TrustedServers is needed .local/share/barrier/SSL/Fingerprints/TrustedServers.txt. The file should contain the SSL fingerprint.

@ERasnier commented on GitHub (Apr 16, 2021): I'm getting a refused connection from the ssh command but on the server logs it's saying that client connection has been accepted. The server logs endlessly repeats the idea that two client connections has been accepted but disconnects. EDIT: Fixed. This it works completely now but a note that installing through snap is in a different directory than normal and a file called TrustedServers is needed `.local/share/barrier/SSL/Fingerprints/TrustedServers.txt`. The file should contain the SSL fingerprint.