-
Notifications
You must be signed in to change notification settings - Fork 69
Project name selection error #553
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
If the project type is Workers and you've had a NuxtHub account prior to us releasing that feature, you'll need to add the Worker Scripts permission to your Cloudflare token. https://hub.nuxt.com/changelog/workers#deploying-to-workers |
@RihanArfan Thanks for the reply, but this is a new NuxtHub organization and a new Cloudflare account. I generated the token tonight, and Workers is properly enabled. ![]() |
I had the exact issue with my deployments (See #548), the only difference was: mine was an old account, so the |
Hi @maximepvrt, thanks for raising this issue. I've investigated and I believe the the issue is your account doesn't have a workers.dev subdomain set yet. Please could you go to https://dash.cloudflare.com/?to=/:account/workers/workers-and-pages. Opening the Workers & Pages landing page for the first time should create a workers.dev subdomain automatically. We'll add checks for this to prevent the issue happening for others too. Let me know whether that works. |
Hi, yes you're absolutely right. I just visited the Workers & Pages page (correct url: https://dash.cloudflare.com/?to=/:account/workers-and-pages) and it did create the |
Description
When trying to create a new project on hub.nuxt.com I consistently get an error saying the project name is already taken, even when using an extremely specific and unlikely-to-be-used name (e.g.,
ballancetonde-website2zzzzzzzzqqezaeaqsdf23456734567
).Steps to Reproduce
"The project name ... is taken. Please choose another name."
Expected Behavior
The system should accept a project name that is clearly unique.
Screenshot
Notes
I tried with several variations and always got the same message, as if the backend name check is failing or misbehaving.
The text was updated successfully, but these errors were encountered: