Can't deploy - WinRM timeout on first vm

[mjakubowskilkr]

I've tried with Debian 12 & Kali Linux. I can't install GOAD (full), deploy stops at GOAD-DC01: WinRM transport: negotiate Then it's timeout - how to fix it?

[r4ulcl]

Hi, I solved it with this issue: #160

https://github.com/Orange-Cyberdefense/GOAD/blob/main/docs/troubleshoot.md#vagrant-up---winrm---digest-initialization-failed--initialization-error

[mjakubowskilkr]

I've tried all methods, method 1: now it's timeout on WinRM transport: plaintext, method 2 does nothing. When I downgraded vagrant (method 3), I had to downgrade VirtualBox to 6.1 but it doesn't start - no kernel modules, dkms only for 7.x in repository. Any idea? These 2 machines are vms on Proxmox, they are set as host and virtualization works on them.

[Mayfly277]

Vagrant fail to intiate the winrm connection (see : https://github.com/hashicorp/vagrant/issues/13211#issuecomment-1601665940). Have you tried with the last version of vagrant ? (not the one from debian repo)

[mjakubowskilkr]

I've tried. The same.

[Mayfly277]

can you try to vagrant up a simple machine out of goad project ?

like :

vagrant init mayfly/windows_server2019 \
  --box-version 2023.10.19
vagrant up

and tell me what append ?

[mjakubowskilkr]

Should I run it from GOAD main directory?

When I run it, I got smth like below (but I try to run in on virtualbox): Vagrant encountered an unexpected communications error with the

Vagrant VMware Utility driver. Please try to run the command

again. If this error persists, please open a new issue at:

https://github.com/hashicorp/vagrant-vmware-desktop/issues

From: Mayfly @.> Sent: Wednesday, April 3, 2024 9:28 PM To: Orange-Cyberdefense/GOAD @.> Cc: mjakubowskilkr @.>; Author @.> Subject: Re: [Orange-Cyberdefense/GOAD] Can't deploy - WinRM timeout on first vm (Issue #202)

can you try to vagrant up a simple machine out of goad project ?

like :

vagrant init mayfly/windows_server2019 \ --box-version 2023.10.19 vagrant up

and tell me what append ?

— Reply to this email directly, view it on GitHub https://github.com/Orange-Cyberdefense/GOAD/issues/202#issuecomment-2035416546 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGAIK4BALOHIZCZ7T5DUBBLY3RJ23AVCNFSM6AAAAABFKWOKRSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMZVGQYTMNJUGY . You are receiving this because you authored the thread. https://github.com/notifications/beacon/AGAIK4D45XHLTTD36V7HQ2DY3RJ23A5CNFSM6AAAAABFKWOKRSWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTTZKH66E.gif Message ID: @. @.> >

[mjakubowskilkr]

Should I run it from GOAD main directory?

When I run it, I got smth like below (but I try to run in on virtualbox): Vagrant encountered an unexpected communications error with the Vagrant VMware Utility driver. Please try to run the command again. If this error persists, please open a new issue at:

https://github.com/hashicorp/vagrant-vmware-desktop/issues

[Mayfly277]

ok so try something like that :

• create a new folder outside goad :

  cd ~
  mkdir testvm
  cd testvm

• create a Vagrantfile like that :

Vagrant.configure("2") do |config|
  ENV['VAGRANT_DEFAULT_PROVIDER'] = 'virtualbox'
  config.vm.box = "mayfly/windows_server2019"
end

• and than run vagrant up
• if the vm is well download and loaded all is fine in your configuration if not there is an issue on your vagrant install.

[mjakubowskilkr]

It's problem with vagrant - the same timeout as while GOAD deploy.