Common errors
Reference for common error messages in StoreFrame — what they mean, why they happen, and how to fix them.
This page lists the error messages you may encounter in the Hub, along with their cause and fix. If you see an error not listed here, file a support ticket with the exact message text.
Provisioning and environment creation
"No trial slots available. You can only have one active trial at a time."
Cause: You already have an active trial environment. StoreFrame allows one concurrent trial per organization.
Fix: Destroy your existing trial in the Hub before starting a new one, or upgrade the existing trial to a paid Project.
"No project slots available. Please upgrade your subscription to add more production environments."
Cause: All purchased Project slots are in use. Slot usage is computed from the number of active (non-destroyed) production environments in your organization.
Fix: Either destroy an existing production environment to free a slot, or go to Settings → Organization → Billing to add more Project slots.
"No stage slots available. Please upgrade your subscription to add more staging/develop/test environments."
Cause: All purchased Stage slots are in use.
Fix: Either destroy an existing stage environment, or go to Settings → Organization → Billing to add more Stage slots.
"No environment slots available. Add an environment slot in billing settings before creating a stage environment."
Cause: Attempting to create a Stage environment (staging, develop, or test) when no stage slots are available and the payment method cannot add one automatically.
Fix: Add a Stage slot in Settings → Organization → Billing, then retry.
"This environment subdomain is already in use. Please choose a different suffix." / "This subdomain is already taken."
Cause: The subdomain you entered is already assigned to another environment within the system.
Fix: Choose a different subdomain in the wizard. Subdomains within storeframe.store must be globally unique.
"Provider authentication not found"
Cause: The wizard cannot find a cloud provider token for your organization. This is required for paid Project and Stage environments (not for Trials, which run on StoreFrame infrastructure).
Fix: Go to Settings → Organization → Providers, add your cloud provider API token, and restart the wizard.
"Platform configuration not found"
Cause: The Magento platform configuration required to provision the environment is missing or incomplete. This is usually a transient internal error.
Fix: Retry the provision. If the error persists, file a support ticket.
"Trial environments cannot create additional environments. Upgrade to production first."
Cause: You attempted to create a Stage environment with a trial as the parent. Only Production environments can have Stage children.
Fix: Upgrade your trial to a paid Project first, then create Stage environments under it.
"Environment must be active to create additional environments"
Cause: You tried to create a Stage environment while the parent is in a non-active state (Provisioning, Failed, Suspended, etc.).
Fix: Wait for the parent environment to reach "Active" status, then retry.
"Only production environments can create additional environments"
Cause: The parent environment type is not "production" (e.g., it is a staging environment). Stages can only be children of production environments.
Fix: Select a production environment as the parent when creating a Stage.
"Environment must be active or failed to destroy"
Cause: You attempted to destroy an environment that is in the middle of a transition (e.g., still provisioning).
Fix: Wait for the current operation to complete, then retry the destroy action.
"Environment must be active to resize"
Cause: Resize operations can only be run on active environments.
Fix: Ensure the environment is in "Active" status before resizing.
"Trial has expired and cannot be subscribed. Please create a new trial."
Cause: Your trial's grace period has elapsed. Expired trials cannot be converted to paid Projects — the conversion window has passed.
Fix: Start a new trial, or contact support if you believe the expiry was in error.
Access and permissions
"Insufficient permissions"
Cause: Your organization role (Member) does not have the access level required for the action. Certain actions — adding provider tokens, inviting members, modifying billing — require the Admin role.
Fix: Ask an organization owner or admin to perform the action, or to upgrade your role.
"Only owners can transfer ownership."
Cause: Ownership transfer is restricted to the current organization owner.
Fix: The current owner must initiate the transfer from Settings → Organization → Members.
"Owners cannot be removed."
Cause: You attempted to remove the organization owner from the member list. An owner must first transfer ownership to another member before they can be removed.
Fix: Transfer ownership first, then remove the old owner.
"Invitation was revoked"
Cause: The invitation link you clicked was cancelled by an admin before you accepted it.
Fix: Ask an admin to send a new invitation.
"Invitation already accepted"
Cause: The invitation was already used. Each invite link is single-use.
Fix: If you accepted the invite and cannot access the organization, check that you are logged in with the same email address the invite was sent to.
"Already member or invited"
Cause: You tried to invite an email address that already has membership or a pending invitation in the organization.
Fix: Check the existing member list and pending invitations in Settings → Organization → Members.
"Member limit reached. Your plan allows a maximum of N members."
Cause: Your subscription plan has a maximum team-size limit and you have reached it.
Fix: Upgrade your plan to allow more members, or remove an existing member to make room.
"Email address is already taken"
Cause: When updating your account email, the new address is already registered to another StoreFrame account.
Fix: Use a different email address.
SSH keys
"SSH key not found"
Cause: You referenced an SSH key that does not exist — it may have been deleted before the operation completed.
Fix: Refresh the page and check the SSH key list. Re-add the key if needed.
When nothing matches
If the error message you are seeing is not listed here, copy the exact text and file a support ticket. Include the environment ID (visible in the URL), the time the error occurred (UTC), and what you were doing when it appeared.