We’ve recently enabled read-only workspaces for users that don’t have access to premium resources anymore (aren’t paying, cancelled plan, etc). We did this so we can restrict access to users without having to delete code, that way everyone’s code can stay safe even if they’re not premium
With that, there are two potential causes for the issue you’re seeing:
- We are incorrectly counting SSH workspaces as premium workspaces, therefore potentially preventing you from creating/accessing premium, private, or SSH workspace that your plan allows for.
- While we momentarily (and mistakenly) stopped enforcing the RAM limit that your plan includes, we now enforce that again, so you can’t resize workspaces to have more than is allotted on your plan. If you already have workspaces that violate your plan limits, you’ll be locked out of those.
To give us some time to fix point 1 and you some time to fix point 2, reach out to us via support available to premium users at https://c9.io/support and we’ll give you a week trial on the unlimited plan (after verifying the situation). Within that time period, we should have the quota issues worked out and you’ll be able to go back to your normal plan then.
Note: During this trial period, you’ll be able to boost workspaces to have more RAM. Be very careful with this because if you decide to remain on your current legacy plan when the trial expires then you’ll be locked out of those workspaces since they’re using more RAM than you have on your plan. Then you’ll have to signup for premium