Discussions

Any ideas how to go about this error ?

``` 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.

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?

How can I troubleshoot this issue?

Would be nice to be able to choose the default region the labs get deployed into

Hi! I'm trying to start labs but when I click on Start button, labs is not working and show this message: We couldn't power off those instances right now because some are already busy. Anyone can help me?

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

I started the course recently and my lab time is already over. My understanding was that lab is available for 6 months from start of the course. Is that not the case?

I have an issue where when I try to start the RTO labs, it states that it cannot be done as some resources are busy. I can start each individually, but when I last did this, the squid proxy didn't start, which impacts progression in the lab

Hi! Does snaplabs have an API to invoke a lab creation? Thanks!