- Newest
- Most votes
- Most comments
If you are using minimal instance types such as t2.micro or t3.small, scaling up instance type may improve this.
same (and im not hosted on AWS) I think they just broke cloud9 and wont bother ever fixing it. I recommend moving to a different IDE and hosting provider.
I had the same problem and unfortunately I wasn't able to find a solution.
I tried stopping/restarting the instance, figuring that moves it to a different physical host and might fix it. But no luck.
I increased the instance size and disk size but that didn't help either. (The instance was fine, I could ssh into it and it still ran all the services. Only the IDE was messed up.)
I waited until the next day, figuring maybe it was a temporary issue. No luck there.
Ultimately I rebuild a new cloud9, reinstalling everything again. Not as bad as it sounds, at least for me, as we have templates and scripts to do most of the work. But still disappointing and I wasted half a day on this.
Hi,
Thanks for the response. I found the issue went away on its own, then re-appeared for a couple of days and then went away again. I haven't seen it in a while now. Not sure why/how either unfortunately.
I hope it continues to work OK for you.
Mark
Here too!
After a few days I just happened to launch my original cloud9 environment that was having this issue and it's gone now.
Whatever. :)
Relevant content
- asked a year ago
- asked a year ago
- AWS OFFICIALUpdated 4 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago