Forum Discussion

ijunki3's avatar
ijunki3
Bronze II
1 year ago
Solved

Cannot seem to connect to Snaplabs via VPN

Hello, I’ve spun up a Snaplabs range - it’s a templated range based on shirts. I seem to be having trouble connecting to it though: I’ve added a VPN and tried to connect to it from several endpoin...
help & support
  • ijunki3's avatar
    ijunki3
    1 year ago

    Hi Dave, have a new data point for you: looking at my AWS account today I see that there are AdminBox instances that correspond to the instances of shirts and eagle bank that I spawned before. They were not visible in snaplabs though. Stranger still, when I terminated those ranges, these adminbox instances not only did not terminate but they were also switched on. 

    I noticed that when I create Shirts or Eagle Bank, I see that the Range is always marked as "Starting". Could it be that it cannot create AdminBox due to some resource limitation or something?

    I tried creating an introductory range, which I believe is just an AdminBox and a DC. This seems to do the trick.

    Any insight would be appreciated, but I seem to be unblocked at this point!

doctax's avatar
doctax
New Member I
3 hours ago

Hi,

Can you please clarify what the resolution for this issue was?

I'm facing the same issue trying to spin up an 'Eagle Bank' range, where the adminbox isn't being deployed. 

I don't see it listed in the range template system details table either.

Similar to you, my Eagle Bank range is marked as "Launching" rather than "Running".

From what I can see the only range that actually starts an adminbox when deployed is the "Introductory Range"

I understand that the VPN goes through the adminbox, meaning that I can't VPN into the network, nor console into any of the machines through guacamole.