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

Private Key Authentication Failure #13483

Open
Aijaz-Qureshi opened this issue Aug 1, 2024 · 0 comments
Open

Private Key Authentication Failure #13483

Aijaz-Qureshi opened this issue Aug 1, 2024 · 0 comments

Comments

@Aijaz-Qureshi
Copy link

Debug output

https://gist.github.com/Aijaz-Qureshi/e77f5029f5b1b80a9ba5712d515de179.js

Expected behavior

It shouldn't show the Authentication Failure because I've downloaded the vagrant.pub and uploaded it to my box.

Actual behavior

I am able to login via Ubuntu Desktop and Vagrant ssh, but I am getting the Private Key Authentication Failure errors.

Here's the GitBash output from the project folder:


XXXXXXXXXX@XXXXXXXXXX MINGW64 /d/vagrant/projects/projectAQ
$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'aijazqureshi/Ubuntu2404-Desktop-LTS-amd64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'aijazqureshi/Ubuntu2404-Desktop-LTS-amd64' version '1.0' is up to date...
==> default: Setting the name of the VM: projectAQ_default_1722542874531_72234
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
default: SSH address: 127.0.0.1:2222
default: SSH username: vagrant
default: SSH auth method: private key
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...

default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...
default: Warning: Authentication failure. Retrying...

Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest machine within
the configured ("config.vm.boot_timeout" value) time period.

If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.

If you're using a custom box, make sure that networking is properly
working and you're able to connect to the machine. It is a common
problem that networking isn't setup properly in these boxes.
Verify that authentication configurations are also setup properly,
as well.

If the box appears to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.

XXXXXXXXXX@XXXXXXXXXX MINGW64 /d/vagrant/projects/projectAQ
$ vagrant ssh
[email protected]'s password:
[email protected]'s password:
Welcome to Ubuntu 24.04 LTS (GNU/Linux 6.8.0-39-generic x86_64)

Expanded Security Maintenance for Applications is not enabled.

0 updates can be applied immediately.

8 additional security updates can be applied with ESM Apps.
Learn more about enabling ESM Apps service at https://ubuntu.com/esm

The programs included with the Ubuntu system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Ubuntu comes with ABSOLUTELY NO WARRANTY, to the extent permitted by
applicable law.

vagrant@noble:~$

Reproduction information

Vagrant version

Vagrant 2.4.1

Host operating system

Windows 11

Guest operating system

Ubuntu Desktop LTS 24.04

Steps to reproduce

  1. Download and save the Vagrantfile for "aijazqureshi/Ubuntu2404-Desktop-LTS-amd64" from Vagrant Cloud
  2. Vagrant up
  3. Inspect the Vagrant.log file

Vagrantfile

Vagrant.configure("2") do |config|
  config.vm.box = "aijazqureshi/Ubuntu2404-Desktop-LTS-amd64"
end
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant