Unable to connect to AWS lightsail ubuntu server throw SSH
Clash Royale CLAN TAG#URR8PPP
up vote
0
down vote
favorite
I am not able to connect to Ubuntu server. Its on AWS lightsail. I gave permission to the pem file through chmod 600 command. I created new Keypair but still not able to connect.
OpenSSH_7.7p1, LibreSSL 2.7.3 debug1: Reading configuration data
/etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 48: Applying
options for * debug1: Connecting to 35.161.126.138 [35.161.126.138]
port 22. debug1: Connection established. debug1: permanently_set_uid:
0/0 debug1: key_load_public: No such file or directory debug1:
identity file
/Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem type -1
debug1: key_load_public: No such file or directory debug1: identity
file /Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem-cert
type -1 debug1: Local version string SSH-2.0-OpenSSH_7.7 debug1:
Remote protocol version 2.0, remote software version OpenSSH_7.6p1
Ubuntu-4 debug1: match: OpenSSH_7.6p1 Ubuntu-4 pat OpenSSH* compat
0x04000000 debug1: Authenticating to 35.161.126.138:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key
algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher:
chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC:
compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:jI80AzLJamFx2iImMR5ArTzlGKtGCWE8Ydmt4Qyc8Zg debug1: Host
'35.161.126.138' is known and matches the ECDSA host key. debug1:
Found key in /var/root/.ssh/known_hosts:7 debug1: rekey after
134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting
SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after
134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1:
kex_input_ext_info:
server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that
can continue: publickey debug1: Next authentication method: publickey
debug1: Trying private key:
/Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem debug1:
Authentications that can continue: publickey debug1: No more
authentication methods to try. ubuntu@35.161.126.138: Permission
denied (publickey).
linux ubuntu ssh aws
asked 9 mins ago
Waqas
1
New contributor
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
0
down vote
favorite
I am not able to connect to Ubuntu server. Its on AWS lightsail. I gave permission to the pem file through chmod 600 command. I created new Keypair but still not able to connect.
OpenSSH_7.7p1, LibreSSL 2.7.3 debug1: Reading configuration data
/etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 48: Applying
options for * debug1: Connecting to 35.161.126.138 [35.161.126.138]
port 22. debug1: Connection established. debug1: permanently_set_uid:
0/0 debug1: key_load_public: No such file or directory debug1:
identity file
/Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem type -1
debug1: key_load_public: No such file or directory debug1: identity
file /Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem-cert
type -1 debug1: Local version string SSH-2.0-OpenSSH_7.7 debug1:
Remote protocol version 2.0, remote software version OpenSSH_7.6p1
Ubuntu-4 debug1: match: OpenSSH_7.6p1 Ubuntu-4 pat OpenSSH* compat
0x04000000 debug1: Authenticating to 35.161.126.138:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key
algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher:
chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC:
compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:jI80AzLJamFx2iImMR5ArTzlGKtGCWE8Ydmt4Qyc8Zg debug1: Host
'35.161.126.138' is known and matches the ECDSA host key. debug1:
Found key in /var/root/.ssh/known_hosts:7 debug1: rekey after
134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting
SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after
134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1:
kex_input_ext_info:
server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that
can continue: publickey debug1: Next authentication method: publickey
debug1: Trying private key:
/Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem debug1:
Authentications that can continue: publickey debug1: No more
authentication methods to try. ubuntu@35.161.126.138: Permission
denied (publickey).
linux ubuntu ssh aws
asked 9 mins ago
Waqas
1
New contributor
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am not able to connect to Ubuntu server. Its on AWS lightsail. I gave permission to the pem file through chmod 600 command. I created new Keypair but still not able to connect.
OpenSSH_7.7p1, LibreSSL 2.7.3 debug1: Reading configuration data
/etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 48: Applying
options for * debug1: Connecting to 35.161.126.138 [35.161.126.138]
port 22. debug1: Connection established. debug1: permanently_set_uid:
0/0 debug1: key_load_public: No such file or directory debug1:
identity file
/Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem type -1
debug1: key_load_public: No such file or directory debug1: identity
file /Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem-cert
type -1 debug1: Local version string SSH-2.0-OpenSSH_7.7 debug1:
Remote protocol version 2.0, remote software version OpenSSH_7.6p1
Ubuntu-4 debug1: match: OpenSSH_7.6p1 Ubuntu-4 pat OpenSSH* compat
0x04000000 debug1: Authenticating to 35.161.126.138:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key
algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher:
chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC:
compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:jI80AzLJamFx2iImMR5ArTzlGKtGCWE8Ydmt4Qyc8Zg debug1: Host
'35.161.126.138' is known and matches the ECDSA host key. debug1:
Found key in /var/root/.ssh/known_hosts:7 debug1: rekey after
134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting
SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after
134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1:
kex_input_ext_info:
server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that
can continue: publickey debug1: Next authentication method: publickey
debug1: Trying private key:
/Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem debug1:
Authentications that can continue: publickey debug1: No more
authentication methods to try. ubuntu@35.161.126.138: Permission
denied (publickey).
linux ubuntu ssh aws
asked 9 mins ago
Waqas
1
New contributor
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I am not able to connect to Ubuntu server. Its on AWS lightsail. I gave permission to the pem file through chmod 600 command. I created new Keypair but still not able to connect.
OpenSSH_7.7p1, LibreSSL 2.7.3 debug1: Reading configuration data
/etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 48: Applying
options for * debug1: Connecting to 35.161.126.138 [35.161.126.138]
port 22. debug1: Connection established. debug1: permanently_set_uid:
0/0 debug1: key_load_public: No such file or directory debug1:
identity file
/Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem type -1
debug1: key_load_public: No such file or directory debug1: identity
file /Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem-cert
type -1 debug1: Local version string SSH-2.0-OpenSSH_7.7 debug1:
Remote protocol version 2.0, remote software version OpenSSH_7.6p1
Ubuntu-4 debug1: match: OpenSSH_7.6p1 Ubuntu-4 pat OpenSSH* compat
0x04000000 debug1: Authenticating to 35.161.126.138:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256 debug1: kex: host key
algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher:
chacha20-poly1305@openssh.com MAC: compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC:
compression: none debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256
SHA256:jI80AzLJamFx2iImMR5ArTzlGKtGCWE8Ydmt4Qyc8Zg debug1: Host
'35.161.126.138' is known and matches the ECDSA host key. debug1:
Found key in /var/root/.ssh/known_hosts:7 debug1: rekey after
134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting
SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey after
134217728 blocks debug1: SSH2_MSG_EXT_INFO received debug1:
kex_input_ext_info:
server-sig-algs=
debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that
can continue: publickey debug1: Next authentication method: publickey
debug1: Trying private key:
/Users/waqas80/Documents/EnfocarSoft/awskeys/awsoregon.pem debug1:
Authentications that can continue: publickey debug1: No more
authentication methods to try. ubuntu@35.161.126.138: Permission
denied (publickey).
linux ubuntu ssh aws
linux ubuntu ssh aws
asked 9 mins ago
Waqas
1
New contributor
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 9 mins ago
Waqas
1
New contributor
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 9 mins ago
Waqas
1
New contributor
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
asked 9 mins ago
Waqas
1
asked 9 mins ago
Waqas
1
1
New contributor
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Waqas is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
add a comment |Â
add a comment |Â
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Waqas is a new contributor. Be nice, and check out our Code of Conduct.
Waqas is a new contributor. Be nice, and check out our Code of Conduct.
Waqas is a new contributor. Be nice, and check out our Code of Conduct.
Waqas is a new contributor. Be nice, and check out our Code of Conduct.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f476949%2funable-to-connect-to-aws-lightsail-ubuntu-server-throw-ssh%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
