-
-
Notifications
You must be signed in to change notification settings - Fork 516
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
Telepresence connect returns telepresence connect: error: connector.Connect: failed to connect to root daemon: rpc error: code = DeadlineExceeded desc = context deadline exceeded #3350
Comments
This seems to be an issue with DNS. What Windows version are you using? |
@thallgren this occurs on both Windows 10 and Windows 11, the exact versions differ a bit, but the problem is the same. |
same issue.(M1 Mac)
|
@east-shine I don't think this is the same issue. You encounter a panic on a M1. Can you please create a new issue? |
The M1 panic (actually, it affects all darwin systems) is addressed in PR #3474. |
@dfilipov-anakatech would you care to try with the new 2.19.0 release? It contains some improvements that might impact this. |
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
A clear and concise description of what the bug is.
When trying to 'telepresence connect' we get the error message
'telepresence connect: error: connector.Connect: failed to connect to root daemon: rpc error: code = DeadlineExceeded desc = context deadline exceeded'
None of the telepresence functionality is thus available.
Running 'telepresence loglevel debug' leads to the same exact error, so I cannot provide more verbose logs than the default.
We are using an OpenVPN server and client and this problem only occurs on Windows machines
connector.log
The text was updated successfully, but these errors were encountered: