Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Teleport connect v14 crash on launch #50602

Open
fullpolarfox opened this issue Dec 28, 2024 · 2 comments
Open

Teleport connect v14 crash on launch #50602

fullpolarfox opened this issue Dec 28, 2024 · 2 comments
Labels
bug teleport-connect Issues related to Teleport Connect.

Comments

@fullpolarfox
Copy link

Expected behavior:
When launch Teleport Connect application, it starts up

Current behavior:
After update Teleport connect app from 13.4.11 to 14.3.33 it crash on startup with error
Image

Also tried v15.4.22, got same error. After downgrade to 13.4.11 app works fine
Deleting dir AppData\Roaming"Teleport Connect"\ will not help

Platform: vmware VM with windows 10

Bug details:

  • Teleport version
    Teleport v14.3.33
  • Recreation steps
    Install the new version and launch it.
  • Debug logs
    main.log
    tshd.log
    shared.log
@zmb3 zmb3 added the teleport-connect Issues related to Teleport Connect. label Dec 29, 2024
@ravicious
Copy link
Member

The error message doesn't help much because of how AggregateError returned by Promise.any gets serialized to string. But the code that fails is related to reading C:\Users\<user\AppData\Roaming\Teleport Connect\certs\renderer.crt.

readGrpcCert(certsDir, GrpcCertName.Renderer),

return await Promise.any([watchForFile(), checkIfFileAlreadyExists()]);

Alas, you've already said that removing the whole Teleport Connect user data directory doesn't help. The code that fails hasn't been modified since v12 at least, so I suspect it's either something related to an updated version of Electron (and thus Node.js) or something specific to your setup.

There's not much we can debug further without more error information unfortunately. Given that it's another instance of Promise.any biting us with an unclear error message, I'm inclined to create a wrapper which makes sure that the underlying errors do end up in the logs. This would help us move forward on this issue. I unfortunately cannot promise when this will happen as I'm busy with other tasks, but I'll keep this issue in mind.

@ravicious
Copy link
Member

#50640 makes sure we don't lose error information. It'll be included in the next v15 and v16 release, but in the meantime, could you try running Teleport Connect v17.1.4 to see if that PR helps with identifying the problem?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug teleport-connect Issues related to Teleport Connect.
Projects
None yet
Development

No branches or pull requests

3 participants