Note: Please go to to access the current RightScale documentation set. Also, feel free to Chat with us!
Home > Guides > Dashboard Users Guide > Clouds > AWS Regions > VPCs > Actions > VPC Troubleshooting

VPC Troubleshooting

Table of Contents


Due to RightScale Legacy Platform deprecation, this section covering Amazon Web Services Virtual Private Clouds (VPC) is no longer valid. Please see the Network Manager section for current information on creating and managing AWS VPCs.

If you have problems when setting up VPCs, check to see if you are experiencing one of the following issues.



  • Servers are stuck in the ‘booting’ state for a long time (20 minutes or more).
    • Your application, database, and other servers should be in your private subnets.
    • Make sure that the server is in the correct subnet. Servers in the public subnet need an EIP and the public subnet needs an Internet gateway.
    • Make sure that the NAT host is running and that it can connect to the Internet.  
    • Check the private network route tables and route sets.  
    • Make sure the CIDR IP for the Private Route Set is (and not
    • Check that the VPC NAT host is associated to the private route table.
  • Servers in the public network do not boot.
    • Make sure the public route table has the Internet gateway set up

    • Make sure the servers have EIP’s attached.

    • Make sure the CIDR IP for the Public Route Set is (and not

  • Route Set has blackhole for the gateway.
    • This is caused by the VPC Nat Host being terminated or removed.  To correct this issue, update the Route Set to point to the new VPC Server.
You must to post a comment.
Last modified
12:11, 3 Nov 2014



This page has no classifications.



© 2006-2014 RightScale, Inc. All rights reserved.
RightScale is a registered trademark of RightScale, Inc. All other products and services may be trademarks or servicemarks of their respective owners.