debauchee / barrier

Open-source KVM software
Other
27.32k stars 1.5k forks source link

Barrier stuck on "Barrier is starting" on macbook pro, running monterey #1483

Open dzigner opened 2 years ago

dzigner commented 2 years ago

What happened?

I have installed barrier on windows 11 laptop as server, and mac os monterey laptop as client. It works on windows, but on macbook, it stays on saying "barrier is starting". I cannot see it in the screens and links screen.

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)

macOS

What OS versions are you using?

Windowsj 11 and MacOs Monterey

Relevant log output

No response

Any other information

No response

AllysonOfficial commented 2 years ago

See here - https://github.com/debauchee/barrier/discussions/1494 Tested using Windows 10, Windows 11, 3 Mac machines. On Monterrey you will need to install the SSL and create that self certificate to the machine so that the PEM SHA1 RSA key is created as the server looks for it to start the application. This is probably also noted in your log file when you start the application. Hope this helps.

dzigner commented 2 years ago

@AllysonOfficial thankyou But that also didn't help. It is still stuck on Barrier is starting. Do I have to check the boxes for SSL and client certificate?

Secondly, I am having issues now on Windows 11 machine too (as server). That is also stuck on the same thing.

AllysonOfficial commented 2 years ago

@dzigner As for the Windows machines, I had to check the boxes for the SSL for it to work. But for all my mac machines none of them have boxes for ssl either server or client, and i'm using the latest release found here:

https://github.com/debauchee/barrier/releases v2.4.0

Mac and Windows

Here is mine on Monterrey after fresh install on DMG - With the SSL installed as i mentioned in my instructions: Screen Shot 2022-01-04 at 4 56 10 PM

On Windows I don't have any screenshots, however I did follow the same instructions I created for OS X but used the Windows PS for W10/W11 command to install a x509 certificate using OpenSSL. Which after that, and putting in the file required (.pem) in the proper folder in Windows and restarting the application and checking the box it worked just fine. If you have issues when it's "Starting" you can right click on the task bar in either OS X or Windows and on the icon right click and go to "Show Log" this will show you where it's failing and stopping.

LayersOfAbstraction commented 2 years ago

@AllysonOfficial G'day I've been looking at every resource to connect Windows 10 to MacOS Monterey would like to know where you acquired the steps to enter the command for:

Windows PS for W10/W11 command to install a x509 certificate using OpenSSL. Which after that, and putting in the file required (.pem) in the proper folder in Windows and restarting the application and checking the box it worked just fine

I can connect Windows 10 server to the client and it reports it is running and I have been able to generate SSL fingerprint on Mac but I cannot connect the client to the server.

Got a log if anyone can advise me how to resolve this, please.

2022-03-24T09:45:03] INFO: SSL fingerprint generated.

[2022-03-24T09:45:17] INFO: starting client
[2022-03-24T09:45:17] INFO: config file: /private/var/folders/xc/t71x_2n177n97v17lm1jpmlw0000gn/T/Barrier.ukPIdc
[2022-03-24T09:45:17] INFO: log level: INFO
[2022-03-24T09:45:17] INFO: drag and drop enabled
[2022-03-24T09:45:17] NOTE: started client
[2022-03-24T09:45:17] NOTE: connecting to '192.168.56.1': 192.168.56.1:24800
[2022-03-24T09:45:17] INFO: OpenSSL 3.0.0 7 sep 2021
2022-03-24 09:45:17.573 barrierc[1377:20276] starting cocoa loop
[2022-03-24T09:45:32] WARNING: failed to connect to server: Timed out
[2022-03-24T09:45:33] NOTE: connecting to '192.168.56.1': 192.168.56.1:24800
daafonsecato commented 2 years ago

Downgrading to 2.3.3 was initially working but after the first try it went crazy and stop working 😔

daafonsecato commented 2 years ago

Got it working!! It was a whitespace in the Server IP!! 🤣

kenwang92 commented 1 year ago

Got it working!! It was a whitespace in the Server IP!! 🤣

How to fix it? I have same problem.

zippydan commented 1 year ago

My answer here may help you.