mirror of
https://github.com/debauchee/barrier.git
synced 2026-05-15 14:16:02 -06:00
[GH-ISSUE #1743] Current Barrier 2.4.0 not working #1286
Labels
No labels
HiDPI
bounty
bsd/freebsd
bsd/openbsd
bug
bug
build-infra
cantfix
critical
doc
duplicate
enhancement
fix-available
from git
from release
good first issue
help wanted
installer/package
invalid
linux
macOS
meta
needs testing
pull-request
query
question
regression
regression
v2.4.0
windows
wontfix
work-in-progress
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/barrier#1286
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @Ricotta99 on GitHub (Aug 12, 2022).
Original GitHub issue: https://github.com/debauchee/barrier/issues/1743
What happened?
I followed all the procedures to remove any impediment e.g. disabled the ssl settings,allowed windows defender to not temper with it. But nothing.Its keeps saying ''Barrier is running.'' Both machines runs windows 10 ,the server is a lenovo desktop and the client is a lenovo thinkpad t480.
FYI this is my first time using barrier.
Does anyone know if older versions are working?
Version
v2.4.0
Git commit hash (if applicable)
No response
If applicable, where did you install Barrier from?
Github
What OSes are you seeing the problem on? (Check all that apply)
Windows
What OS versions are you using?
Windows 10
Relevant log output
No response
Any other information
No response
@Ricotta99 commented on GitHub (Aug 12, 2022):
ok I tried 2.3.3
nothing,same issue
@fhoshino commented on GitHub (Aug 13, 2022):
Check your firewall settings
@UndyingSisyphos commented on GitHub (Sep 5, 2022):
I just installed it and noticed the same issue, I first thought I would have had to open the port but it seemed weird since it runs in LAN, then looking at the logs I saw that no SSL configuration file was found and it couldn't connect to a secure socket.
The simple solution to make it work is to go (in all server and client machines) to "Barrier" (Tab on the top left) > "Change Settings" > Untick the "Enable SSL" option (and also untick the "Require client certificate" option if ticked), press "OK" and "Reload" and it should work instantly. This obviously makes it less secure but as long as you use it only in LAN it shouldn't be a problem, so be sure port 24800 is NOT OPEN. If you don't know what port forwarding is then it's already closed by default so don't worry.
@Exiliant commented on GitHub (May 11, 2023):
Also make sure to add the clients correct name on the server side....