Repository navigation
Conversation
… entry Added details for setting the provider in the Vercel dashboard and updated troubleshooting sections for better clarity.
| RivetError: No runner config with name 'default' are available in any datacenter for the namespace '...' | ||
| ``` | ||
|
|
||
| Rivet has no provider named `default` for the namespace yet. In the dashboard, open **Settings → Providers** and check that a provider named `default` is listed. If not, add one with your deployment URL (see Register the URL). |
There was a problem hiding this comment.
🟠 Medium · Troubleshooting omits the datacenter configuration that triggers this error
This error also occurs when default exists but is not enabled in any datacenter—the error itself says no config is available in any datacenter, and the registration step above makes selecting one mandatory. In that state, this guidance tells the reader only to confirm that the provider is listed and then offers no fix. Have the reader edit default and verify/select at least one datacenter as well as checking that the provider exists.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Deploying to Vercel with Rivet Cloud, I couldn't find where to register the URL (the step says "in the dashboard") and hit
No runner config with name 'default'with nothing in Troubleshooting. This adds the dashboard path and one troubleshooting entry.Question, not changed in this PR: after registering I also saw
actor.no_runner_config_configuredonce. It stopped after I enabled more datacenters, but a later test with only Northern Virginia on a new actor also worked, so I couldn't isolate the cause. Happy to add an entry if you can tell me what triggers it.Separately, an older version of this guide documented deploying a Hono app (
vercel.jsonframework setting,.tsimports). This page now mentions only Next.js. Happy to restore that in a follow-up if you want it.I used AI help to draft the wording and checked each change against my own deployment.