Server Refused our key - AWS | Tech Arkit

preview_player
Показать описание
Server Refused our key Error another solution which worked for me.

While doing this procedure you need to remember two things

1. Remove the Boot device tag from device after attached
2. Attach EBS volume with /dev/sda1

Youtube PlayLists

Follow Us on Social Media
Рекомендации по теме
Комментарии
Автор

Really awesome, i have gone through AWS document and tried to config in USER DATA, but no luck.. You saved my day. Thank you for sharing the information to ALL.

coolgooglyrahul
Автор

Thank you for identifying the issue. it was very helpful. An alternative to do could be login with ssm manager and do the same activity with out removing the volume. if SSM user folder permission is also modified then this video is the last resort

naveenkumar-yobg
Автор

Thank you SO much! It is very clear. I was completely stuck out of the instance and you saved me!.

regispouillot
Автор

Hi, you are able to enter into the machine when from putty you try to connect to the instance the first time, my problem instead happen when I try to access to the machine after I created the machine on AWS console....I'm obtaining No supported authentication methods available (server sent: publickey, gssapi-keyex, gssap-with-mic)...do you know how can I resolve it?

profumi
Автор

If you are having problems connecting also check these:
1. Ensure you set your IP address when defining your ssh and http settings in ec2 instance. There are online tools to check your IP address.
2. Ensure your anti virus is not having issues with your internet connection or the anti virus vpn is not connected/resolved. You should actually do this before No.1 above but it's not always the case. Note: If your anti virus was recently reconnected/reset check your IP address again and update it in your instance settings.
3. When using Putty Gen application do not click the generate key button rather load your .pem file and just save it as a private key.
4. Do not use paraphrase on the Putty Gen app because it could potentially delay the connection.

Finally you can save your connection when connecting to Putty so that you don't repeat the process of specifying your public DNS and private key.

Hope this helps.

thehumanchannel
Автор

Is there a version of this in english?

Dylan_thebrand_slayer_Mulveiny
Автор

Awsome thanks you so much 😊
You saved my life I got this issue on prod server and your video helped 🙏🏻

holaguys
Автор

Thank u so much it worked appreciate your time !!!

vrakash
Автор

Can you show the demo for adding new user to EC2 instance using putty

harshithac
Автор

I just tried to launch a new instance but got this warning: "You will not be able to connect to this instance as the AMI requires port(s) 1433 to be open in order to have access. Your current security group doesn't have port(s) 1433 open."

befree
Автор

without fs type how can we mount with /mnt we will give file system then all the data will be delete

sandeepgiri
Автор

2nd machine..I have created... connected to Putty.. not connecting same error

yogeshgundale
Автор

thank you, thank you, and again thank

OmriPorat_clinical-dietitian