Unable to Access VM After Changing Instance Type to e2-small

[rmanz13]

Issue:
I can't access my VM after resizing to e2-small.
What I’ve Tried:
Checked network configuration and firewall rules.
Ran traceroute; the connection stops at hop 5.
Tried accessing from different devices and networks.

Error Messages:
"Connection timed out"
"No route to host"

Additional Information:
VM worked fine before resizing to e2-small.
Instance region: [Insert region]
No issues with firewall or network settings.

[reinc]

Hi @rmanz13,

Welcome to Google Cloud Community! 

Here are some relevant documentation that might help:

1. "Connection Timed Out" or "No Route to Host":
This error indicates the VM isn't reachable over the network. It often points to problems with:

• Insufficient Instance Resources - The e2-small instance might not have enough resources (CPU, memory, network bandwidth) for your workload. This is the most probable culprit based on your description.
• Incorrect VPC Configuration - Problems with the Virtual Private Cloud (VPC) network, subnet, or firewall rules.
• Serial Console Configuration - Primary tool for troubleshooting, since it can bypass networking issues.

GCP Documentation:

• Troubleshoot full disks and disk resizing
• Troubleshooting VM Connection Issues
• VPC Troubleshooting
• Serial Console Documentation

2. Possible VM Stuck in "Updating" or "Repairing":
Indicates the resize operation is failing to complete in GCP's backend.

GCP Documentation:

• Troubleshooting Windows VMs
• Apply configuration updates during repairs
• About repairing VMs for high availability 
• Viewing Operation Status 
• Troubleshooting VM Startup Issues 

Also, It appears that additional assistance is required for your project. For more detailed guidance, please contact our support team.


Was this helpful? If so, please accept this answer as “Solution”. If you need additional assistance, reply here within 2 business days and I’ll be happy to help.