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

ssh issue: Warning: Remote connection disconnect. Retrying... #30

Open
abennani31 opened this issue Apr 3, 2023 · 1 comment
Open

Comments

@abennani31
Copy link

HI,

I'm using host with centos8 and virtualbox. I upgarde versions in install command.

When doing Vagrant up, I'm getting connection error to the first vm ( repo):

repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: Warning: Remote connection disconnect. Retrying...
repo: 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.

I tried also with user/password and get the same error.

However, repo vm is stared and can be reached from virtualbox directory but it's configuration is not complete ( network pour adapter 2)

Regards

@abennani31
Copy link
Author

Using root user for vagrant operations fix the problem.
Why this is not working with a regular user?

Regards,

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