SSH Error- Permission denied (publickey,gssapi-keyex,gssapi-with-mic)

-

 Problem-  The authenticity of host 'IP X.X.X.X' can't be established.

ECDSA key fingerprint is SHA256:U8lQ0PvPeWJgvTWC+MHS2Idjt4ZxcDzoW5/7kwJ60X0.

ECDSA key fingerprint is MD5:2f:73:20:11:42:5e:02:8a:65:5a:f3:e1:2c:f8:ad:57.

Are you sure you want to continue connecting (yes/no)? yes

Warning: Permanently added 'host IP' (ECDSA) to the list of known hosts.

Permission denied (publickey,gssapi-keyex,gssapi-with-mic).


Solution- Sometimes it happens we face above issue while making SSH connection between 2 servers or hosts.

Step 1- Make sure ssh server is running 

Step 2- Make some configuration changes in SSHD_Config file accordingly.

Goto- vi /etc/ssh/sshd_config here we need to make 3 changes

1.Uncommet line- PasswordAuthentication yes

2. Commet Line - #PasswordAuthentication no (This will be line number three)

3. Uncommet- PermitRootLogin yes

Step 3- Restart service to apply these changes

service sshd restart



Comments

Post a Comment

Popular posts from this blog

Deploying App through AWS EKS by using ingress and fargate

-
Image
 1.Create cluster Command-  eksctl create cluster --name demo-cluster --region us-east-1 --fargate (15 to 20 min) 2. Once cluster is ready check if it is visible in EKS 3. aws eks update-kubeconfig --name demo-cluster --region us-east-1 output- Added new context arn:aws:eks:us-east-1:533267033126:cluster/demo-cluster to C:\Users\Raghvendra Singh\.kube\config 4. creating fargate profile Command (linux)- eksctl create fargateprofile \          --cluster demo-cluster \          --region us-east-1 \          --name alb-sample-app \          --namespace game-2048 windows- eksctl create fargateprofile --cluster demo-cluster --region us-east-1 --name alb-sample-app --namespace game-2048 5. Application deployment- kubectl apply -f https://raw.githubusercontent.com/kubernetes-sigs/aws-load-balancer-controller/v2.5.4/docs/examples/2048/2048_full.yaml 6. After deploying this app, run few c...
Read more

How to enable AWS EBS Volume snapshots encryption

-
Using the AWS console: Sign in to AWS console and navigate to https://console.aws.amazon.com/ec2/ From the left navigation choose snapshots option. Select the actionable snapshot, choose actions. Choose the Copy Snapshot option. Check the encryption option. Under the Master key choose the kms key (It is recommended to choose KMS CMK when EBS snapshot consist of highly sensitive data). Click on copy. Once the newly encrypted snapshot is ready old snapshot should be deleted. Using AWS CLI $> aws ec2 copy-snapshot --description [description-for-new-snapshot] --destination-region [region-name] --encrypted --kms-key-id [kms-key-id] ---source-region [region-name] --source-snapshot-id [actionable-snapshot-id] Command reference: https://docs.aws.amazon.com/cli/latest/reference/ec2/copy-snapshot.html $> aws ec2 delete-snapshot --snapshot-id [actionable-snapshot-id] --region [region-name] Command reference: https://docs.aws.amazon.com/cli/latest/reference/ec2/delete-snapshot.html Note: App...
Read more

Reset Jenkins Admin Password

-
Image
  Stop Jenkins: On Linux, use sudo service jenkins stop. On Windows, stop the Jenkins service from the Services window. Access the Jenkins Home Directory: By default, the home directory is located at /var/lib/jenkins/ on Linux and %JENKINS_HOME% on Windows. Remove the config.xml for Security: In the Jenkins home directory, locate the config.xml file. Open it in a text editor and search for the <useSecurity> tag. Change the value to false: xml Copy code <useSecurity>false</useSecurity> File will look like below- Save the file and exit. Start Jenkins: Start Jenkins again (sudo service jenkins start for Linux). Jenkins should now start without asking for a login, and you can create a new user or reset the credentials. Re-enable Security: Once you've logged in and set up new credentials, go back to the config.xml file. Set <useSecurity> back to true and restart Jenkins to enable security again.
Read more