Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unable to SSH - "Server Refused Our Key" #32

Open
anweiss opened this issue Feb 4, 2015 · 1 comment
Open

Unable to SSH - "Server Refused Our Key" #32

anweiss opened this issue Feb 4, 2015 · 1 comment

Comments

@anweiss
Copy link

anweiss commented Feb 4, 2015

I'm working on adding Microsoft Azure support for this project and am running in to an SSH issue that I can't seem to figure out. Upon attempting to SSH into a VM created from this image, the server fails to accept my key. I generated the cert/key with openssl as follows:

openssl req -x509 -nodes -days 365 -newkey rsa:2048 -keyout myKey.key -out myCert.pem
chmod 600 myKey.key

The public cert subsequently gets uploaded via the Azure portal and placed in ~/.ssh/authorized_keys.

This issue doesn't seem to be related to packer-azure since I'm able to SSH into an image that's created without any Packer provisioners. This only seems to occur after the Chef recipe is applied via the chef-solo provisioner.

@ghost
Copy link

ghost commented Aug 17, 2016

I'm having the exact same problem, used Cygwin to create the key, fed it into Puttygen, used the saved key with Putty, and I'm getting the same error message

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant