# Broken my fly ssh console command **URL:** \ **Category:** General\ **Created:** [February 16, 2022, 9:52pm UTC](https://community.fly.io/t/broken-my-fly-ssh-console-command/4101 "2022-02-16T21:52:22Z")\ **Posts on this page:** 1\ **Showing post:** 2
**Author:** ![greg](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/greg/32/2119_2.png) [@greg](https://community.fly.io/u/greg)\ **Post date:** [February 16, 2022, 11:25pm UTC](https://community.fly.io/t/broken-my-fly-ssh-console-command/4101/2 "2022-02-16T23:25:13Z")
Hmm. Assuming you are on the latest version of the CLI, you could try `fly doctor` … and see what that says. Given that `... failed probing "name": context deadline exceeded` error, that sounds like an error other people have had (in their case when deploying, but I assume it affects _all_ commands). Maybe take a look at this (it’s a long thread). Maybe the IPv6 affects the peer or how the innards work: > [@Deployments not working: error connecting to docker](https://community.fly.io/t/deployments-not-working-error-connecting-to-docker/3992/48): > > Thanks to debugging help from @kim, we tracked this down to a regression in how flyctl handles wireguard peers that have been reaped in our backend, but are still active locally. While we’re working on a fix, here’s a way you can try to fix it for now: Stop the fly agent with fly agent stop Remove the wireguard peer entry from ~/.fly/config.yml for the organization you’re having trouble with, including the org name key. Start the agent and try fly ping -a orgname If this works, deploys sho… --- _[View the full topic](https://community.fly.io/t/broken-my-fly-ssh-console-command/4101)._