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!
ImmerserCan you confirm that you are in the us-east-1 region in AWS? If you are then I will need to do some investigations
Bronze IIHi 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!
- DaveSpencer
I am glad you are unblocked on this, and I have passed the additional details to the engineering team who are investigating the issue. All extra data points help.
Thank you for bearing with us while we get this right.
