-
Notifications
You must be signed in to change notification settings - Fork 501
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
Windows 11 - connect not working #3279
Comments
Hi @gabriel-lafreniere, looking at error (An attempt was made to access a socket in a way forbidden) could this perhaps be a port conflict as noted here? |
@cindymullins-dw
telepresences services are setup like below as well
|
@mgialelis-pm , it might be an issue with the Cloudflare VPN. The relevant docs page is here. You could try checking your routing table and if possible manually adding the routes as here, if that's an option for you. |
Hello everyone;
Note that I could not run
telepresence loglevel debug
, or gather-logs, since I cannot even properly connect to the telepresence.Version: 2.14.1
Kubectl setup on machines
GCloud setup on machines
We are setting up Telepresence in parallel to Cloudflare Warp, and this seems to be causing issues only Windows machines.
The CLI error that we are getting is:
Although the error logs seem to detail more concrete problems (See logs at the end of this post).
I've tried disabling the firewall, with no conclusions.
Any
connect
tentative on a Windows machine seems to be failing.I am mainly hoping anybody could think of any specific known issue seeing the logs?
Something that seems off to me is:
Because the equivalent command works with kubectl
kubectl get namespaces --watch
Logs
connector logs
daemon logs
The text was updated successfully, but these errors were encountered: