I am able to ssh to system@xxx.cloudapp.azure.com with no problems using the keys I created when deploying the instance. The system account had no existing keys so I used scp to copy the generated keys to the jump box. Next I tried to ssh to one of the cluster nodes, but that fails as follows:
The documentation does confirm that you have to SSH to the jump box then SSH to a specific node. See https://confluence.atlassian.com/enterprise/administering-jira-software-data-center-on-azure-969535567.html
I ran into the same issue and was able to resolve the issue this way:
Now, connections from the JumpBox to the cluster node should be accepted.
Connecting to JumpBox from your machine:
ssh -i ~/.ssh/jumpbox_key user@jumpbox.westus2.cloudapp.azure.com
Then, connecting to the node from JumpBox:
ssh -i ~/.ssh/node_key user@10.0.2.5
My expectation from experience here is you should have the public key from the jump server already present on the Node you are trying to access because only then would the authentication process work here. This is different from your personal public key.
If the instance is already up and running, I will check with whoever has access to grant the jump server access to the nodes. They can then share this with you so you can access it.
The above suggestion is based on my understanding that you connect to a jump server and from the jump server, you connect to a server hosting the different Jira nodes.
Regards.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.