Forum Discussion
Bronze IICannot seem to connect to Snaplabs via VPN
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!
ImmerserHi,
The lack of an AdminBox would very much be the problem as that handles the routing and the VPN. Can you check within your AWS instance to see if it exists within it?
Thanks
Dave
Bronze IIHi Dave,
Thanks for your reply - indeed, I don’t seem to have an AdminBox in my setup. How would I add it? I can’t see any option to do this.
- DaveSpencer
There definitely isn't a method to add a new AdminBox, however all isn't lost.
As most of your range is built from the Shirts template , you can create images of the hosts you have added/modified (https://docs.snaplabs.io/docs/systems-apps#image) and then deploy a fresh shirts template and add the missing/modified hosts from the created images- ijunki3
Thanks! I’ll try that out.
- ijunki3
Ok so really strange: when I try to spin up a new shirts range, the admin box doesn’t get spun up either. In fact, if I try to spin up another range like eagle bank I don’t get an admin box either. Any recommendations?
- DaveSpencer
Can you confirm that you are in the us-east-1 region in AWS? If you are then I will need to do some investigations
- DaveSpencer
There isn't a way to add an AdminBox as far as I know, but let me look into it and see if there is something we can do.
