Notebook labs troubleshooting
Last updated 1 Nov 2026
Overview
This article collects messages you may see when creating labs, managing rosters, signing in to a hub, or using the individual pay-per-hour hub. Wording comes from CloudPe APIs and hub spawn checks; the dashboard often shows the same text in a toast or under a roster row.
Before you start
- Note the lab name, region and the exact message.
- For student issues, confirm roster Status on the lab Members table.
Steps
Lab not available or blocked at spawn
This lab is not available for your account right now.(hub spawn) — You are not an active lab member, the lab is not active, billing blocked spawns, or your organisation balance exhausted seat billing. Faculty: check lab status and Notebook labs billing. Students: ask your instructor to confirm you are active on the roster.
Create lab errors
region not enabled— Notebooks is off for that region or the organisation is not entitled. Pick another region or contact support.slug already in use— Choose a unique slug.unknown plan,unknown image,invalid or reserved slug— Fix the create form values; slugs must be valid DNS labels.
Roster and invitations
Member invitation cannot be resent— Resend works only for invited or invite_failed rows. Remove the member and import again, or wait for acceptance.- invite conflict (status pill) — The email has a pending organisation invitation. Resolve on Team or cancel one of the invites.
- invite failed — Read last_error under the member; fix the email or resend.
CSV must be 1 MiB or smaller.— Use a smaller file.
Sign-in and access
- Cannot sign in to the hub — Roster must be active; country and IP allow-list rules apply. Students are not org members but still inherit org geo/IP policy tied to the lab.
- Dashboard shows only Notebooks — Normal for lab-only students; open that page to reach labs.
Individual hub refusals
prepaid wallet required— Pick a prepaid organisation with balance, or top up the wallet.not allowed to use notebooks— Missingnotebooks:useor membership in the billing org.one session at a time— Stop the other running individual server.billing blocked— Overdue invoices or wallet policy blocked usage.- Individual hub card hidden on Notebooks — Postpaid org, zero balance, ineligible region, or missing permission.
Sessions and admin actions
Lab is not ready— Lab still provisioning or not active; wait and retry.cannot stop another user's session— Only stop your own server unless you manage the lab and use the lab Stop control on Sessions.session already ended— Refresh the sessions list.
Open in CloudPe
- Repository rejected — Only https URLs on allowed public hosts (GitHub, GitLab, Hugging Face). Fix the link or branch/path parameters.
If none of the above applies, contact support with organisation id, lab slug, screenshot of the message, and time (UTC).
Did this guide answer your question?If you need customized assistance with your deployment, reach out to our team.
Contact Support
