No config options

[ylluminate]

No config options

[ylluminate]

I compiled the current project and now it seems that I can connect and config Options... appear again once I enable encryption on both sides. I think after I do this the first time I am then able to disable or reenable encryption.

[egirsova]

Hi George,

Yes, the issue was resolved in the previous two commits but it hasn't been added to an official release yet. Your best bet is to build the project yourself.

The issue actually occurred because it couldn't find the desktop background image. So, if you want to use the latest official release, your other option would be to change your desktop background to a static image that exists on your computer.

Otherwise, we'll have to sit tight and wait for an official release with the latest changes.

[ylluminate]

Hey Liza, I did build it from the current src, but are there a couple more commits that aren't in master yet? Appreciate your chiming in on this!

[egirsova]

No, should all be there. They're just not part of the official release. Are you still unable to connect? What system are you running?

[dwt]

Out of interest: Is there already a date planned for an official release?

[ylluminate]

Okay... So I wanted to get back now here after fiddling for a few days with it.

First, I have found that it will not connect unless I have encryption turned on (there is seemingly no way to make this work without encryption; I can turn it on, connect and then turn it off, but it will not work otherwise it appears).

Second, if the system starts with it, I usually have to go to Configure... first before it will start working again.

Third, it seems that it is a bit crashy. After I shut down a client machine, I had teleport crash on the main system / host:
https://gist.github.com/ylluminate/ba3d33aff974ce6143032da083d394ce

Of course you can see from that that Im running 10.11.6.

[egirsova]

@dwt, I'm not actually the main developer of the project so I don't know.

@ylluminate, I think I may have had the same issue that you were describing but I haven't had the chance to look into it. Unfortunately I currently don't have access to two machines so I'm unable to help investigate further. It would be good to submit it as a separate issue from this though.

[johndbritton]

@egirsova mentioned that the original issue here was resolved. I haven't been able to reproduce.

The latest release v1.2.2 is working on macOS Big Sur. Give it a try, if you have any problems please open an issue with full steps to reproduce.