Ask a Question

Creating a snapshot

How can i create a snapshot for the environement?

Terminated VM

One of the VMs in my training course is shown as "Terminated". I can't access any of the options to Start or Snapshot - they are greyed out. How do I restart this VM?

issues with openvpn connection

I'm trying to connect to my lab as attacker. My lab is on (AdminBox rebooted several times) and I can't connect to my lab. Is there an option that i missed?. I create openvpn conf on my profile for linux (using kali to connect).

On Snaplabs-AD-quickstart how does one login to admin box?

On Snaplabs-AD-quickstart how does one login to admin box? I'm using AD Quickstart - Server 2019 Functional Level template

Lab stuck at "Templating"

Hello, I tried to create a template of my lab but it seems stuck at "templating". I can not find any way to stop this process. Is there anything I can do? I can not see anything happening on the aws side either. Best, Martin

Stuck at Launching Labs

I have a problem with launching either shirt corp or eagle bank in the sense that most of the VMs are stuck at launching state and didnt even get created at AWS EC2 instances, i've incresaed my cpu to 120 vcpu but still have face the problem. A little help would be appreciated. Thank you.

wkstn-2069.child.rto.local doestn reconnect

Hello, The machine wkstn-2069.child.rto.local is not connecting and I am losing exam time, I have tried restarting it, stopping it and starting it again and nothing, any solution? Thank you!

Unable to GUI or SSH into Machines.

``` Failed to connect to remote access server. If you've just powered on your lab environment, please try again in a few minutes.``` This is the Error message I get whenever I try to SSH or GUI login into a Machine I have inside a lab. I am able to connect to the machines with the vpn/public IP setup/ but unable to get the browser based Guacamole Login screen. This Happens only with one Lab, My other lab is working fine. I tried Rebooting the Lab.

Eage Bank is broken on community version

Hi - I've gone through several attempts to start EagleBank, but every time some machines are not created at all (are hung in <launching> state in the console) - aws clearly shows the VM is not created. Some are - but are still stuck in <lauching> state even after manually rebooting them in aws. I guess for some cases the provisioning dependencies will be broken. Could SnapLabs staff get a look at this, or at least advise on how to debug it. My CloudFormation stack has been created a while ago - does it make sense to re-create it?

adminBox for each lab

AWS creates a public IP of each AdminBox's. We can access via web guacamole but the credentials are not clear since they are not documented in the lab templates. Thanks, x0341