AWS Cloud9 Environment Trouble Connecting

Attach the volume from the broken instance to the new instance as a separate volume and pull off the information you need. You can also look around at the logs to see if you can find the root cause.

Thank you this worked a treat for me, much appreciated !!

Can you please take a look at this document - https://docs.aws.amazon.com/cloud9/latest/user-guide/vpc-settings.html and ensure the network settings for your Cloud9 are correctly configured.

There is also a blog that you can refer to - https://aws.amazon.com/blogs/security/isolating-network-access-to-your-aws-cloud9-environments/

Having exactly the same issue here, haven't been able to connect to a cloud9 instance that has been working fine for months. No recent changes were made to the VPC settings at all. I've tried changing instance type from T3.medium to T3.large, to T3.xlarge as well as setting the Capacity Reservation settings to None, and altering the credit specification to be enable unlimited mode. I'm out of ideas and have work on the instance I nee

I've seen this behavior. I fixed it by clearing my browser cache and cookies. Not sure what the root cause was.

Sorry I'm just back from vacation and tried clearing cache and cookies but didn't help unfortunately.

The latest thing I've tried to at least be able to access my data is to

• create a snapshot image of the failing cloud9 env/ec2
• create a new cloud9 environment and make sure I can connect to it (all good)
• stop the new env, detach the new EBS volume
• created a new volume from the snapshot image of the old failing cloud9
• attach the new volume to the new cloud9 environment
• try to connect - again we time out due to high CPU / burstable credits / VPC config despite being able to connect before switching volumes

I'm starting to get worried about this as I will need to access some work off the old instance soon.
Any other suggestions welcome

I'm having a similar problem where an environment that was working now is giving me strange issues like be extremely slow in terminals, constantly 'Reconnecting' etc. I don't want to attempt all that work if it didn't help things for you - how did it go?

Thanks,

Mark

One other thing I would advise is reviewing the EC2 console logs [1] of your instance to see if there are any clear signs of failed startup, disk space running out, etc. I've recently run into a scenario where disk space had run out on the underlying EBS volume resulting in failures starting necessary processes for Cloud 9.

[1] EC2 Console Logs - https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/instance-console.html#instance-console-console-output