Torubles with the Pro

[csimpi]

Hi, thank you for your vagrant boxes.
I've used the free version of scotch box for years. I purchased the pro, I'm trying to switch but I'm getting strange bugs during configuring the Pro version.

After the first vagrant up the ssh key doesn't work anymore, I don't know why.

    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. 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.

vagrant provision output

Guest-specific operations were attempted on a machine that is not
ready for guest communication. This should not happen and a bug
should be reported.

After the first vagrant reboot, I'm getting this, I can't get into the box anymore. I don't change anything regarding the ssh things at all. I've tried to destroy the machine and start again, I'm getting this all the time. This is not happening with the free version on the same PC in the same time, I think this is some kind of bug in PRO version.

[whatnickcodes]

https://box.scotch.io/common-questions/

Search "Weird Authentication Issues"

[whatnickcodes]

Also, just try uninstalling and reinstalling. It's weird and annoying but works

[csimpi]

Thank you, but that's not an explanation only a hacky solution to avoid and not solve the real problem.

I'm after the reinstalling, I did it many times, I'm still getting this...

I just noticed, If I make a completely raw install, I'm getting this during the very first vagrant up.

    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default: Warning: Connection reset. Retrying...
    default: Warning: Connection aborted. Retrying...
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...

So what is the real fix? I'm not comfortable with hacky solutions, my codes and my entire work into the vagrant machine, so I'd need to be sure about my stuffs won't disappear or something like that...

[csimpi]

After couples of days working without any issue, today I wanted to reload the machine, and I started to get this error message:

There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

vagrant halt, doesn't work either, it didn't drop any message but didn't halt the machine either.

I switched the machine off from VirtualBox, after vagrant up I'm getting the Authentication issue again:

  default: SSH auth method: private key
    default: Warning: Connection aborted. Retrying...
    default: Warning: Remote connection disconnect. Retrying...

Something is bugged with the pro version, I have never got any similar issues with the free version before, I'm switching back to the free :(