johndbritton / teleport

Virtual KVM for macOS
GNU General Public License v2.0
797 stars 134 forks source link

teleport not working at all #102

Closed julian-weinert closed 3 years ago

julian-weinert commented 3 years ago

I'm running teleport on two macs. The Macs show up well, depending on which machine I'm sharing. I can configure the application and place the remotes mac on the layout view. Both Macs run Mojave.

Now how do I use this? In other issues people talked about hot keys, I would suspect it to simply work when I move the mouse over the screen border. But nothing happens.

Further questions. What is keyCombo and why is it required as well as not configurable? Why is there no documentation that hints to a "key combo" I would need to use?

What is hotBorders and why do no hot borders exists when the application is running?

I'm at a total loss with this. I've dug through the complete source, hacked a lot of bools around, tried to remove unnecessary checks and disabling features that are not represented in the UI... Nothing helps. Absolutely nothing.

johndbritton commented 3 years ago

I'm not sure what the issue is in your case, but to help with debugging, you can turn on debug mode for teleport with defaults write com.abyssoft.teleport enableLogging 1.

To disable debug mode, run defaults write com.abyssoft.teleport enableLogging 1.

julian-weinert commented 3 years ago

I'm assuming my issue being not understanding how this software is supposed to work. Isn't it meant to share mouse and keyboard? I should be able to so so then.

When I configure both macs and connect them nothing happens.

julian-weinert commented 3 years ago

When pairing the following logs appear

pairing host 0x600001bad360 id=<MAC> state=1 address=192.168.178.54 rect={{2560, -13}, {1280, 1024}} to screen index 0 with shared screen index 0 position {2560, -13}
<TPConnectionsManager: 0x6000024d0ab0>: -[TPConnectionsManager connectToHost:withDelegate:infoDict:]
updating hot border (null) for host host 0x600001bad360 id=<MAC> state=32 address=192.168.178.54 rect={{2560, -13}, {1280, 1024}}: show: 0 activate: 1

When moving my mouse to the screen border I configured the remote Mac to nothing happens. The mouse is not shared, the keyboard is not shared.

tomads commented 3 years ago

Hi.

You have to enable encryption on both computers by using the same certificate!

If you do that right, the client will ask you for keychain access, when you try to switch for the first time. Allow forever. Same when switching back to the client.

If that wont work for you, it’s probably a problem with yor macs …

Greetz

Am 26.07.2021 um 08:26 schrieb Julian F. Weinert @.***>:

 When pairing the following logs appear

pairing host 0x600001bad360 id= state=1 address=192.168.178.54 rect={{2560, -13}, {1280, 1024}} to screen index 0 with shared screen index 0 position {2560, -13} <TPConnectionsManager: 0x6000024d0ab0>: -[TPConnectionsManager connectToHost:withDelegate:infoDict:] updating hot border (null) for host host 0x600001bad360 id= state=32 address=192.168.178.54 rect={{2560, -13}, {1280, 1024}}: show: 0 activate: 1 When moving my mouse to the screen border I configured the remote Mac to nothing happens. The mouse is not shared, the keyboard is not shared.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or unsubscribe.

julian-weinert commented 3 years ago

@tomads thanks a lot! I did not see any mention that encryption is absolutely required... This did the trick. Even though you don't need the same certificate, as it turns out.

@johndbritton it might be useful to add that to the readme :)

johndbritton commented 3 years ago

Interesting. The requirement for encryption may be the result of changes in MacOS.