Permission denied (publickey) on ubuntu 16.04github ssh problem- permission...

How could an armless race establish civilization?

for xml path('') output

How to get a character's limb regrown at 3rd level?

Could this problem be tackled using Mathematica?

Single level file directory

Sharing referee/AE report online to point out a grievous error in refereeing

What do you call a notepad used to keep a record?

Divergent Series & Continued Fraction (from Gauss' Mathematical Diary)

How does the Divination wizard's Expert Divination feature work when you upcast a divination spell?

How did they film the Invisible Man being invisible, in 1933?

Can one use the present progressive or gerund like an adjective?

Find the radius of the hoop.

Can a stressful Wish's Strength reduction be cured early by a Greater Restoration spell?

How to describe POV characters?

I need help with pasta

The warming up game

Company threatening to call my current job after I declined their offer

Script executes loop only once

How do I tell the reader that my character is autistic in Fantasy?

Sacrifice blocking creature before damage is dealt no longer working (MtG Arena)?

What game is this character in the Pixels movie from?

How do we separate rules of logic from non-logical constraints?

Adjective for 'made of pus' or 'corrupted by pus' or something of something of pus

Why wasn't EBCDIC designed with contiguous alphanumeric characters?



Permission denied (publickey) on ubuntu 16.04


github ssh problem- permission denied(publickey)ssh_exchange_identification: read: Connection reset by peerPermission denied (publickey,gssapi-keyex,gssapi-with-mic)SSH publickey permission denied (Google Cloud Platform)SSH Permission Denied Public KeySSH passwordless root login gets “Permission denied (publickey).”SSH publickey login permission denied on CENTOS But not on DebianSSH - Permission denied (publickey)Login loop ubuntu 16.04localhost: Permission denied (publickey,password,keyboard-interactive)






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







0















$ ssh mykey.pem ubuntu@10.128.2.7 -v
OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016
debug1: Reading configuration data /c/Users/works/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 10.128.2.7 [10.128.2.7] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 pat OpenSSH_6.6.1* compat 0x04000000
debug1: Authenticating to 10.128.2.7:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:R+d2ELtCJyoeyHMfivCsGKk98GOIfxxsTEPAFmKkSOI
debug1: Host '10.128.2.7' is known and matches the ECDSA host key.
debug1: Found key in /c/Users/works/.ssh/known_hosts:1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).


I used to be able to ssh into this machine until yesterday.
Is there a way to login into it?










share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?

    – Stefan M
    Feb 8 '18 at 8:01











  • What you are saying is possible. Is there a way to put it back in place? I am running the instance on openstack.

    – Koustubh
    Feb 8 '18 at 8:12


















0















$ ssh mykey.pem ubuntu@10.128.2.7 -v
OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016
debug1: Reading configuration data /c/Users/works/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 10.128.2.7 [10.128.2.7] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 pat OpenSSH_6.6.1* compat 0x04000000
debug1: Authenticating to 10.128.2.7:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:R+d2ELtCJyoeyHMfivCsGKk98GOIfxxsTEPAFmKkSOI
debug1: Host '10.128.2.7' is known and matches the ECDSA host key.
debug1: Found key in /c/Users/works/.ssh/known_hosts:1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).


I used to be able to ssh into this machine until yesterday.
Is there a way to login into it?










share|improve this question
















bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
















  • Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?

    – Stefan M
    Feb 8 '18 at 8:01











  • What you are saying is possible. Is there a way to put it back in place? I am running the instance on openstack.

    – Koustubh
    Feb 8 '18 at 8:12














0












0








0








$ ssh mykey.pem ubuntu@10.128.2.7 -v
OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016
debug1: Reading configuration data /c/Users/works/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 10.128.2.7 [10.128.2.7] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 pat OpenSSH_6.6.1* compat 0x04000000
debug1: Authenticating to 10.128.2.7:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:R+d2ELtCJyoeyHMfivCsGKk98GOIfxxsTEPAFmKkSOI
debug1: Host '10.128.2.7' is known and matches the ECDSA host key.
debug1: Found key in /c/Users/works/.ssh/known_hosts:1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).


I used to be able to ssh into this machine until yesterday.
Is there a way to login into it?










share|improve this question
















$ ssh mykey.pem ubuntu@10.128.2.7 -v
OpenSSH_7.3p1, OpenSSL 1.0.2j 26 Sep 2016
debug1: Reading configuration data /c/Users/works/.ssh/config
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Connecting to 10.128.2.7 [10.128.2.7] port 22.
debug1: Connection established.
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
debug1: key_load_public: No such file or directory
debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
debug1: Enabling compatibility mode for protocol 2.0
debug1: Local version string SSH-2.0-OpenSSH_7.3
debug1: Remote protocol version 2.0, remote software version OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8
debug1: match: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2.8 pat OpenSSH_6.6.1* compat 0x04000000
debug1: Authenticating to 10.128.2.7:22 as 'ubuntu'
debug1: SSH2_MSG_KEXINIT sent
debug1: SSH2_MSG_KEXINIT received
debug1: kex: algorithm: curve25519-sha256@libssh.org
debug1: kex: host key algorithm: ecdsa-sha2-nistp256
debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
debug1: Server host key: ecdsa-sha2-nistp256 SHA256:R+d2ELtCJyoeyHMfivCsGKk98GOIfxxsTEPAFmKkSOI
debug1: Host '10.128.2.7' is known and matches the ECDSA host key.
debug1: Found key in /c/Users/works/.ssh/known_hosts:1
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS sent
debug1: expecting SSH2_MSG_NEWKEYS
debug1: rekey after 134217728 blocks
debug1: SSH2_MSG_NEWKEYS received
debug1: SSH2_MSG_SERVICE_ACCEPT received
debug1: Authentications that can continue: publickey
debug1: Next authentication method: publickey
debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
debug1: Authentications that can continue: publickey
debug1: No more authentication methods to try.
Permission denied (publickey).


I used to be able to ssh into this machine until yesterday.
Is there a way to login into it?







ubuntu ssh openstack






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Feb 8 '18 at 8:12







Koustubh

















asked Feb 8 '18 at 7:41









KoustubhKoustubh

1389 bronze badges




1389 bronze badges





bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.







bumped to the homepage by Community 1 hour ago


This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.















  • Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?

    – Stefan M
    Feb 8 '18 at 8:01











  • What you are saying is possible. Is there a way to put it back in place? I am running the instance on openstack.

    – Koustubh
    Feb 8 '18 at 8:12



















  • Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?

    – Stefan M
    Feb 8 '18 at 8:01











  • What you are saying is possible. Is there a way to put it back in place? I am running the instance on openstack.

    – Koustubh
    Feb 8 '18 at 8:12

















Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?

– Stefan M
Feb 8 '18 at 8:01





Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?

– Stefan M
Feb 8 '18 at 8:01













What you are saying is possible. Is there a way to put it back in place? I am running the instance on openstack.

– Koustubh
Feb 8 '18 at 8:12





What you are saying is possible. Is there a way to put it back in place? I am running the instance on openstack.

– Koustubh
Feb 8 '18 at 8:12










2 Answers
2






active

oldest

votes


















0














Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?



If you deleted the information, you won't be available to log into the server again, if you don't have physical access to the disk.



This is basic ssh security, if you don't have the appropriate key which is mentioned in the .ssh/authorized_keys, you don't get access. That way you make sure that noone else can easily access your server.






share|improve this answer































    0














    $ ssh mykey.pem ubuntu@10.128.2.7 -v
    ...
    debug1: key_load_public: No such file or directory
    debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
    ...
    debug1: Next authentication method: publickey
    debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
    debug1: Authentications that can continue: publickey


    The only key which your client tried to use is ifx_key.pem. It looks like that file isn't actually present (the "type -1" line). If that's the key which ssh is supposed to authenticate with, make sure the file is actually present on your local system and that you have permission to read it.



    $ ssh mykey.pem ubuntu@10.128.2.7 -v


    This suggests that you want ssh to use a different key file named mykey.pem, but you didn't specify the command correctly. To specify a key on the command line, use the -i option:



    $ ssh -i mykey.pem ubuntu@10.128.2.7 -v





    share|improve this answer


























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "106"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f422725%2fpermission-denied-publickey-on-ubuntu-16-04%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      0














      Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?



      If you deleted the information, you won't be available to log into the server again, if you don't have physical access to the disk.



      This is basic ssh security, if you don't have the appropriate key which is mentioned in the .ssh/authorized_keys, you don't get access. That way you make sure that noone else can easily access your server.






      share|improve this answer




























        0














        Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?



        If you deleted the information, you won't be available to log into the server again, if you don't have physical access to the disk.



        This is basic ssh security, if you don't have the appropriate key which is mentioned in the .ssh/authorized_keys, you don't get access. That way you make sure that noone else can easily access your server.






        share|improve this answer


























          0












          0








          0







          Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?



          If you deleted the information, you won't be available to log into the server again, if you don't have physical access to the disk.



          This is basic ssh security, if you don't have the appropriate key which is mentioned in the .ssh/authorized_keys, you don't get access. That way you make sure that noone else can easily access your server.






          share|improve this answer













          Only if you have a private key that is reference to in the .ssh/authorized_keys on the server. Have you deleted that file or altered its contents?



          If you deleted the information, you won't be available to log into the server again, if you don't have physical access to the disk.



          This is basic ssh security, if you don't have the appropriate key which is mentioned in the .ssh/authorized_keys, you don't get access. That way you make sure that noone else can easily access your server.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Feb 8 '18 at 8:34









          Stefan MStefan M

          9351 gold badge7 silver badges17 bronze badges




          9351 gold badge7 silver badges17 bronze badges

























              0














              $ ssh mykey.pem ubuntu@10.128.2.7 -v
              ...
              debug1: key_load_public: No such file or directory
              debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
              debug1: key_load_public: No such file or directory
              debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
              ...
              debug1: Next authentication method: publickey
              debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
              debug1: Authentications that can continue: publickey


              The only key which your client tried to use is ifx_key.pem. It looks like that file isn't actually present (the "type -1" line). If that's the key which ssh is supposed to authenticate with, make sure the file is actually present on your local system and that you have permission to read it.



              $ ssh mykey.pem ubuntu@10.128.2.7 -v


              This suggests that you want ssh to use a different key file named mykey.pem, but you didn't specify the command correctly. To specify a key on the command line, use the -i option:



              $ ssh -i mykey.pem ubuntu@10.128.2.7 -v





              share|improve this answer




























                0














                $ ssh mykey.pem ubuntu@10.128.2.7 -v
                ...
                debug1: key_load_public: No such file or directory
                debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
                debug1: key_load_public: No such file or directory
                debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
                ...
                debug1: Next authentication method: publickey
                debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
                debug1: Authentications that can continue: publickey


                The only key which your client tried to use is ifx_key.pem. It looks like that file isn't actually present (the "type -1" line). If that's the key which ssh is supposed to authenticate with, make sure the file is actually present on your local system and that you have permission to read it.



                $ ssh mykey.pem ubuntu@10.128.2.7 -v


                This suggests that you want ssh to use a different key file named mykey.pem, but you didn't specify the command correctly. To specify a key on the command line, use the -i option:



                $ ssh -i mykey.pem ubuntu@10.128.2.7 -v





                share|improve this answer


























                  0












                  0








                  0







                  $ ssh mykey.pem ubuntu@10.128.2.7 -v
                  ...
                  debug1: key_load_public: No such file or directory
                  debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
                  debug1: key_load_public: No such file or directory
                  debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
                  ...
                  debug1: Next authentication method: publickey
                  debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
                  debug1: Authentications that can continue: publickey


                  The only key which your client tried to use is ifx_key.pem. It looks like that file isn't actually present (the "type -1" line). If that's the key which ssh is supposed to authenticate with, make sure the file is actually present on your local system and that you have permission to read it.



                  $ ssh mykey.pem ubuntu@10.128.2.7 -v


                  This suggests that you want ssh to use a different key file named mykey.pem, but you didn't specify the command correctly. To specify a key on the command line, use the -i option:



                  $ ssh -i mykey.pem ubuntu@10.128.2.7 -v





                  share|improve this answer













                  $ ssh mykey.pem ubuntu@10.128.2.7 -v
                  ...
                  debug1: key_load_public: No such file or directory
                  debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem type -1
                  debug1: key_load_public: No such file or directory
                  debug1: identity file /c/Users/works/Documents/interface setup/ifx_key.pem-cert type -1
                  ...
                  debug1: Next authentication method: publickey
                  debug1: Trying private key: /c/Users/works/Documents/interface setup/ifx_key.pem
                  debug1: Authentications that can continue: publickey


                  The only key which your client tried to use is ifx_key.pem. It looks like that file isn't actually present (the "type -1" line). If that's the key which ssh is supposed to authenticate with, make sure the file is actually present on your local system and that you have permission to read it.



                  $ ssh mykey.pem ubuntu@10.128.2.7 -v


                  This suggests that you want ssh to use a different key file named mykey.pem, but you didn't specify the command correctly. To specify a key on the command line, use the -i option:



                  $ ssh -i mykey.pem ubuntu@10.128.2.7 -v






                  share|improve this answer












                  share|improve this answer



                  share|improve this answer










                  answered Feb 8 '18 at 14:29









                  KensterKenster

                  1,5241 gold badge8 silver badges12 bronze badges




                  1,5241 gold badge8 silver badges12 bronze badges






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to Unix & Linux Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f422725%2fpermission-denied-publickey-on-ubuntu-16-04%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      Popular posts from this blog

                      Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                      Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                      Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...