[GH-ISSUE #1004] Barrier client's can't connect to sever #802

New issue

Closed

opened 2026-05-05 07:09:40 -06:00 by gitea-mirror · 2 comments

gitea-mirror commented

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

Owner

Originally created by @PedroNestor2077 on GitHub (Jan 6, 2021).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1004

i've be using barrier a long time, but this never happens

barrier client log:
[2021-01-06T15:27:05] WARNING: failed to connect to server: No route to host
[2021-01-06T15:27:06] NOTE: connecting to '192.168.1.11*': 192.168.1.11*:24801
[2021-01-06T15:27:06] INFO: OpenSSL 1.1.1 11 Sep 2018

running barrier 2.3.3.2 on linux ubuntu 20.10 client and sever

please someone help me

Originally created by @PedroNestor2077 on GitHub (Jan 6, 2021). Original GitHub issue: https://github.com/debauchee/barrier/issues/1004 i've be using barrier a long time, but this never happens barrier client log: [2021-01-06T15:27:05] WARNING: failed to connect to server: No route to host [2021-01-06T15:27:06] NOTE: connecting to '192.168.1.11*': 192.168.1.11*:24801 [2021-01-06T15:27:06] INFO: OpenSSL 1.1.1 11 Sep 2018 running barrier 2.3.3.2 on linux ubuntu 20.10 client and sever please someone help me

gitea-mirror closed this issue

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

gitea-mirror commented

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

Author

Owner

@albertony commented on GitHub (Jan 6, 2021):

Does the log say exactly that? How are you addressing the server? Hostname, IP, with/without port number? I'm wondering about the '192.168.1.11*', not a valid address, and non-default port number 24801..

@albertony commented on GitHub (Jan 6, 2021): Does the log say exactly that? How are you addressing the server? Hostname, IP, with/without port number? I'm wondering about the `'192.168.1.11*'`, not a valid address, and non-default port number 24801..

gitea-mirror commented

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

Author

Owner

@VNRARA commented on GitHub (May 4, 2021):

For ppl coming onto this issue later: Try disabling SSL in both client and server

@VNRARA commented on GitHub (May 4, 2021): For ppl coming onto this issue later: Try disabling SSL in both client and server

gitea-mirror referenced this issue

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

[PR #803] [MERGED] Regenerate server certificate when it is broken or has too small key size #1700