Cant connect to cloud: Unable to get cloud connect token. This agent will do nothing.
PassionateDeveloper86 opened this issue · comments
This morning all was fine and I could intercept my services as usual.
Now I just have the problem, that I can't connect:
When I enter the connect command:
telepresence connect --namespace one
The response is set:
Connected to context minikube, namespace one (https://127.0.0.1:54447)
But with the command to intercept:
telepresence intercept elasticsearch-service-deployment --port 80:80
I just got a message that hints me that the connect is not set correctly:
Warning: You are executing the "telepresence intercept [flags] <intercept_base_name> [-- ]" command without a preceding "telepresence connect", causing an implicit connect to take place. The implicit connect behavior is deprecated and will be removed in a future release.
Connected to context minikube, namespace default (https://127.0.0.1:54447)
telepresence intercept: error: connector.CanIntercept: rpc error: code = Unavailable desc = no active session
When I see the logs of the traffic manager:
time="2024-04-06T19:49:29Z" level=info msg="Setting cloud connect token from environment" THREAD=/lease-lock-watch
time="2024-04-06T19:49:29Z" level=error msg="Unable to get cloud connect token. This agent will do nothing." THREAD=/lease-lock-watch
I use 2.19.0 in telepresence in Windows 11 on a minikube docker image.
What I tried:
- Restart the computer
- restart minikube
- uninstall / install telepresence helm again
- upgrade telepresence (it says to me 2.19.2 is available but after running the setup, it still stuck on 2.19.0)
- Looking at the https://datawire-oss.slack.com/join/signup?error_user_oauth=domain_signup_invalid_domain#/domain-signup status, but it says all services are up
- create a new cloud account and try it with that
Nothing works.
You are running into the problem that we described in the below message on our enterprise slack channel.
🚨 IMPORTANT: We recently discovered an issue in Telepresence CLI versions 2.19.0 through 2.19.1 which may affect Telepresence connectivity. This issue only affects users who have the CLI version 2.19.0. or 2.19.1 installed. The issue noted causes Telepresence to immediately shut down the cloud daemon once it recognizes an available update. This then prevents Telepresence from properly connecting. This issue does not affect users whose clients are air-gapped.
🧰 A fix for this issue is available in Telepresence version 2.19.2. 👀
➡️ If you’re running Telepresence CLI versions 2.19.0 or 2.19.1 we strongly urge you to update to 2.19.2. If you elect to remain on 2.19.0 or 2.19.1 you may prevent the issue by disabling the systray application as described here, but we recommend you upgrade instead.
Telepresence Enterprise Customers with questions or concerns should please contact our Support directly for faster response.
Telepresence version 2.19.2 still has same problem.
My version:
telepresence version
Client : v2.19.2
Root Daemon: not running
User Daemon: not running
k8s version: v1.23.10
traffic-manager-agent-cloud-token:
apiVersion: v1
kind: ConfigMap
metadata:
annotations:
meta.helm.sh/release-name: traffic-manager
meta.helm.sh/release-namespace: ambassador
creationTimestamp: "2024-04-08T09:44:30Z"
labels:
app: traffic-manager
app.kubernetes.io/created-by: Helm
app.kubernetes.io/managed-by: Helm
app.kubernetes.io/version: 2.19.2
helm.sh/chart: telepresence-2.19.2
telepresence: manager
name: traffic-manager-agent-cloud-token
namespace: ambassador
resourceVersion: "4792192"
uid: 6fd413a4-9aea-4a5a-865b-e1363ce5c054
traffic-manager-ambassador-agent logs:
time="2024-04-08T10:33:17Z" level=info msg="Setting cloud connect token from environment" THREAD=/lease-lock-watch
time="2024-04-08T10:33:17Z" level=error msg="Unable to get cloud connect token. This agent will do nothing." THREAD=/lease-lock-watch
agent log:
telepresence connect --proxy-via all=echo
telepresence connect: error: telepresence cloud daemon is not running