This is under construction - a construction period where we will add things as they come to mind... :-)

How do I create an SSH keypair?

Basically, follow this guide smiling face with smiling eyes 

I created a keypair in the Web UI, and windows says "WARNING: UNPROTECTED PRIVATE KEY FILE!" when I try to use the keypair for SSH

The private keys need to have strict enough permissions. In powershell, try:

cmd
icacls .\mykey.pem /inheritance:r
icacls .\mykey.pem /grant:r "%username%":"(R)"
exit

If you still get the same error, then you can fix it with File explorer:

  1. Navigate to the pem-file
  2. Right click the file
  3. Choose properties, security and remove all "Group or user names" other than yourself
  4. Apply, ok

What is my username in my new VM?

It depends. The public Linux based images always has a default user account built-in. See the list here. You always have to login through SSH. These users has no known password set so you need to use the keypair selected when the VM was created. The entire process is described here.

For Windows, you login through RDP with the username "Admin". Read this guide on how to obtain the password.

How do I log in to my VM through the web console?

Short answer: You don't. Mostly because all of the public Linux images are configured with a default user with no known password set. You have to login through SSH and the keypair you specified when the VM was created. Nevertheless, it is possible to either set a password for the default user, or create a new user with a known password, which then will enable you to login through the web console. This will of course have to be done through an SSH connection. That being said, the web console is not meant to be a work surface. It's only a "window" you can look into if something has gone wrong.

For Windows, you will have the password for the "Admin" user account, so you will be able to login. But the same applies here - the web console is not meant to be a work surface.

I can not connect to my VM from WSL2 when I'm connected to Cisco AnyConnect VPN

Sadly, it's a known issue that Cisco AnyConnect breaks WSL2's networking setup.  The current recommended workaround is described in this blog post. If you get issues in step 2 here, a known fix for that is to run the following in a Powershell Window as Administrator

ipconfig /flushdns
# Then run the Get-DnsClientGlobalSetting command again


  • No labels