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

freebsd vagrant does not connect #55

Closed
pmatos opened this issue Jun 13, 2019 · 2 comments
Closed

freebsd vagrant does not connect #55

pmatos opened this issue Jun 13, 2019 · 2 comments

Comments

@pmatos
Copy link

pmatos commented Jun 13, 2019

On arch I run:

$ vagrant init generic/freebsd12
$ vagrant up              
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'freebsd/FreeBSD-11.0-STABLE' version '2017.05.11.2' is up to date...
==> default: Clearing any previously set forwarded ports...
==> 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: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Remote connection disconnect. 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.
@ladar
Copy link
Member

ladar commented Jun 26, 2019

@pmatos you could be facing this issue hashicorp/vagrant#10730 where certain versions of OpenSSH have trouble connecting via NAT. The solution seems to be adding ssh_info_public=true to your Vagrantfile or you can use the VirtualBox GUI to access the box console, and add IPQoS lowdelay throughput to /etc/ssh/sshd_config and restart OpenSSH (or reboot the box). Let me know if that fixes it.

@pmatos
Copy link
Author

pmatos commented Jun 26, 2019

That seems to work. Thanks!

@pmatos pmatos closed this as completed Jun 26, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants