Skip to content

docs(vercel): say where to register the URL and add a troubleshooting entry - #114

Open
k-kj0 wants to merge 3 commits into
rivet-dev:mainfrom
k-kj0:patch-1
Open

k-kj0 wants to merge 3 commits into
rivet-dev:mainfrom
k-kj0:patch-1

Conversation

@k-kj0

@k-kj0 k-kj0 commented Oct 2, 2026

Copy link
Copy Markdown

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_configured once. 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.json framework setting, .ts imports). 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.

k-kj0 added 2 commits October 2, 2026 16:05
… entry

Added details for setting the provider in the Vercel dashboard and updated troubleshooting sections for better clarity.

@the-company-company the-company-company Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 1 medium-severity finding

Reviewed commit 206b0ed.

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).

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟠 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.

@the-company-company the-company-company Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ No issues found

Reviewed commit bedd375.

@k-kj0 k-kj0 changed the title docs(vercel): say where to register the URL and add a troubleshooting entryPatch 1 docs(vercel): say where to register the URL and add a troubleshooting entry Oct 2, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant