From 58b6e355b693bf31fa14cad21bb194aae4e8d704 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 10 Feb 2020 22:37:55 -0700 Subject: [PATCH] Fix formatting issue in troubleshooting page --- .../en/installation/options/troubleshooting/_index.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/content/rancher/v2.x/en/installation/options/troubleshooting/_index.md b/content/rancher/v2.x/en/installation/options/troubleshooting/_index.md index fc1d3ee3b46..556800e0432 100644 --- a/content/rancher/v2.x/en/installation/options/troubleshooting/_index.md +++ b/content/rancher/v2.x/en/installation/options/troubleshooting/_index.md @@ -152,6 +152,8 @@ The most common cause of this issue is the `canal` pods have failed to establish ### Failed to dial to /var/run/docker.sock: ssh: rejected: administratively prohibited (open failed) +Some causes of this error include: + * User specified to connect with does not have permission to access the Docker socket. This can be checked by logging into the host and running the command `docker ps`: ``` @@ -172,16 +174,16 @@ SSH-2.0-OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.10 ### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: no key found -* The key file specified as `ssh_key_path` cannot be accessed. Make sure that you specified the private key file (not the public key, `.pub`), and that the user that is running the `rke` command can access the private key file. +The key file specified as `ssh_key_path` cannot be accessed. Make sure that you specified the private key file (not the public key, `.pub`), and that the user that is running the `rke` command can access the private key file. ### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: ssh: handshake failed: ssh: unable to authenticate, attempted methods [none publickey], no supported methods remain -* The key file specified as `ssh_key_path` is not correct for accessing the node. Double-check if you specified the correct `ssh_key_path` for the node and if you specified the correct user to connect with. +The key file specified as `ssh_key_path` is not correct for accessing the node. Double-check if you specified the correct `ssh_key_path` for the node and if you specified the correct user to connect with. ### Failed to dial ssh using address [xxx.xxx.xxx.xxx:xx]: Error configuring SSH: ssh: cannot decode encrypted private keys -* If you want to use encrypted private keys, you should use `ssh-agent` to load your keys with your passphrase. If the `SSH_AUTH_SOCK` environment variable is found in the environment where the `rke` command is run, it will be used automatically to connect to the node. +If you want to use encrypted private keys, you should use `ssh-agent` to load your keys with your passphrase. If the `SSH_AUTH_SOCK` environment variable is found in the environment where the `rke` command is run, it will be used automatically to connect to the node. ### Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? -* The node is not reachable on the configured `address` and `port`. \ No newline at end of file +The node is not reachable on the configured `address` and `port`. \ No newline at end of file