You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 11, 2019. It is now read-only.
This means you can't house your management box running nscale server outside of your production VPC. In our case, our management server manages all environments (prod, staging, ci etc) which are housed in different VPCs.
I would suggest using the public DNS name if available, as it will resolve to the internal IP if the resolving host is on the same VPC, otherwise it will use the public IP.
The text was updated successfully, but these errors were encountered:
This is critical, and you are absolutely right. Hopefully it will be fixed in the next couple of weeks (I am assembling this week release, and it will not be in there)
This means you can't house your management box running nscale server outside of your production VPC. In our case, our management server manages all environments (prod, staging, ci etc) which are housed in different VPCs.
I would suggest using the public DNS name if available, as it will resolve to the internal IP if the resolving host is on the same VPC, otherwise it will use the public IP.
The text was updated successfully, but these errors were encountered: