Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

4
  • I have ran the command 'ssh-keygen -f test-user-kp.pem -y' and copied the contents into authorized_keys Commented Mar 26 at 8:07
  • The response was ssh - rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCBH6eS7V1yN8FdnXamCvaSCL/YC...........8X1zThpN1JnpwNmR/bH9nwMAe7m....................kt2zw3gsyoWnRP3vod5Bns2LWaXB3o6CW5iWMs9uZ4RmlT/1g+A............................................nc1k4boSoUDqybBLUl6Wypitn23UDT+qQRPgjF+HX1+urSzKix................yr/4v/lXt.....................................F/......................... Commented Mar 26 at 8:10
  • No idea what you are saying above - but the last comment you advised looks like a public key, save for the ''......" bits - which look wrong (ie corrupt)
    – davidgo
    Commented Mar 26 at 17:20
  • Hello, thankyou for your help the problem was that I created the authorized key file as root I used chown and fixed it!!! Running ssh as verbose helped. Commented Mar 26 at 21:59