UlikaDocs
Open Ulika

Getting started

  • Ulika documentation
  • How Ulika works
  • Requirements
  • Quickstart

Connect a site

  • Connect from the dashboard
  • Connect with the CLI
  • Connect with an AI agent
  • Approving a connection
  • Private previews
  • The GitHub App
  • Connect Vercel

Integrations

  • GitHub integration
  • Vercel integration
  • Netlify
  • Claude Code
  • Codex
  • MCP tools

Editing

  • The editor
  • The style panel
  • Sections and pages
  • Mobile preview, autosave and drafts

Publishing

  • Publish your changes
  • History and restoring a version
  • When a publish fails

Team

  • Team roles
  • Inviting people

Projects

  • Project settings
  • Delete a project
  • Website code

Troubleshooting

  • Needs attention reasons
  • Vercel problems
  • GitHub problems
  • CLI errors and exit codes
  • Frequently asked questions

Security and privacy

  • Security and privacy overview

CLI

  • CLI reference
  • CLI changelog

Troubleshooting

Vercel problems

Fix Vercel-related problems when connecting or publishing a site, from ENV_CONFLICT and protected previews to missing projects and deploy hook errors.

Last updated October 14, 2026

Ulika uses your Vercel access for a few jobs: putting a build token on the project (for sites that fetch content when they build), starting and reading the connector's preview build, setting up the deploy hook and webhook that rebuild the site after a publish, and reading protected previews. When one of those steps is refused, Ulika stops with a plain sentence and one fix. This page lists every Vercel problem you can meet and what to do about it.

For how the connection works, see Connect Vercel. Other reasons a connection stops are in Needs attention reasons.

Before you start#

  • Ulika only changes things it created on your Vercel project. It records the ids of what it makes, and it never edits a variable, hook or secret that is yours.

  • Most of the fixes below happen in your own Vercel dashboard, under the project's Settings.

  • Ulika retries temporary errors (Vercel being slow or unreachable, rate limits) by itself. Everything else waits for you; after you fix it, run ulika connect again or press Check again in the browser flow. Nothing is connected twice.

Connecting Vercel#

These are the states of the Connect Vercel card.

not-configured#

What you see. "Connecting Vercel is not set up on this deployment yet."

Why it happens. The Ulika deployment you are using has neither the Vercel integration nor a place to keep pasted tokens configured.

How to fix it. Ask whoever runs your Ulika deployment to set it up. You can still create the branch and open the pull request; open the preview from Vercel yourself.

Retries by itself? No.

not-connected#

What you see. "Connect Vercel first so Ulika can preview the connector on your project." Or, in a pre-check, "Vercel is not connected to this workspace, so Ulika cannot check or prepare the host. Previews will not be verified automatically."

Why it happens. No Vercel access has been saved for the workspace.

How to fix it.

  1. On the connect screen, click Connect Vercel to use the Ulika integration, or open Use an access token instead (advanced).

  2. For a token: on Vercel, create an access token (see Vercel's access token guide for the current steps). Set its Scope to the single team that owns the website, give it a short expiry, copy it, and paste it into Vercel access token.

  3. Click Connect with token.

For sites that publish through Git (new connections), Vercel is optional: connecting it only lets Ulika read previews that ask for a sign-in.

Retries by itself? No.

token-invalid#

What you see. The card title Vercel did not accept the token. "Vercel did not accept that access token. Create a new one, scoped to your team, and paste it again." The same appears as "Vercel did not accept Ulika's saved access. Connect Vercel again." when a saved token stops working.

Why it happens. The token was typed or pasted incorrectly (it must be one string with no spaces), or it was revoked or has expired.

How to fix it.

  1. Create a new token on Vercel scoped to the team that owns the site.

  2. Paste it again and click Connect with token.

  3. If a saved connection stopped working, click Disconnect Vercel and connect again.

Retries by itself? No.

team-not-found#

What you see. "That Vercel team is not visible to this token. Check the team name, or leave it empty to search every team the token can see."

Why it happens. The Team (optional) value does not match any team the token can read.

How to fix it. Use the team name or ID from your Vercel URL, or leave Team (optional) empty so Ulika searches every team the token can see.

Retries by itself? No.

state-invalid#

What you see. "That Vercel link could not be used. It works once and expires after a few minutes. Start again from here."

Why it happens. The one-click Vercel link is single-use and short-lived. Opening it twice, from another browser or after a few minutes fails.

How to fix it. Go back to the connect screen and click Connect Vercel again, finishing in the same browser.

Retries by itself? No.

rate-limited#

What you see. "Vercel is limiting requests right now. Wait a few minutes and try again."

Why it happens. Vercel asked Ulika to slow down.

How to fix it. Wait a few minutes. Inside a connect run, Ulika waits and continues by itself.

Retries by itself? Yes.

unavailable#

What you see. "We could not reach Vercel just now. Try again in a moment." In a failure detail: "Ulika could not reach Vercel (a network failure)" or "Vercel had a server problem (503). Ulika will try again shortly."

Why it happens. A network problem or a Vercel outage. A refusal from Vercel (for example error 400 or 403) is not reported as "could not reach"; Ulika says it was refused.

How to fix it. Check Vercel's status page and try again.

Retries by itself? Yes, up to five times with growing waits.

unexpected-response#

What you see. "Vercel answered, but not in a way Ulika can use. The details below say which call and what was missing; nothing is lost and a re-run is safe."

Why it happens. Vercel returned a successful answer in a shape Ulika did not expect.

How to fix it. Run the connect step again. If it repeats, note the call named in the details when you ask for help.

Retries by itself? No.

request-rejected#

What you see. "Vercel refused a change Ulika asked for on your project. The details below say which one; nothing was written to your repository." In a run: "Vercel understood the request and refused it (400)."

Why it happens. Vercel said no to a specific change: a variable that already exists, a name that is taken, or input it considers invalid. The details line has the step, the call, the status and Vercel's own code. The common one is ENV_CONFLICT below.

How to fix it. Read the details and see the matching section on this page. Nothing was written to your repository.

Retries by itself? No.

Project problems#

vercel-project-not-found#

What you see. The card title We cannot find this website on Vercel. "No Vercel project we can see serves this domain. Check that the token belongs to the team that owns the project." The detail says which account the token belongs to and which teams it looked in. In a pre-check: "No Vercel project in the connected account serves example.com, so there is nowhere to put the build token."

Why it happens. The token (or integration) sees a different team than the one that owns the project, the domain is not added to any project on Vercel, or the project was renamed, moved or deleted.

How to fix it.

  1. On Vercel, open the project and confirm the site's domain is listed under Settings > Domains.

  2. Note which team owns the project.

  3. Create a token scoped to that team (or reconnect with the integration and pick the right team), then connect again.

A Next.js site needs a Vercel project that serves its domain, so this stops the connection until you fix it. Only a Vite or React site that publishes through Git can go on without one: for those Ulika says "No Vercel project ... Ulika will connect it through git alone." (host-not-on-vercel, a warning only). The four reasons a connection waits for Vercel are in Needs attention reasons.

Retries by itself? No.

host-not-on-vercel#

What you see. For a Vite or React site, a warning: "No Vercel project in the connected account serves example.com. Ulika will connect it through git alone."

Why it happens. Your site is hosted somewhere else, or on a Vercel account Ulika cannot see.

How to fix it. Nothing, if you host elsewhere and the site is a Vite or React build that publishes through Git. A Next.js site needs Vercel, so for it this is a blocker, not a warning. If the site is on Vercel, connect the account that owns it.

Retries by itself? Not applicable.

vercel-not-git-linked#

What you see. The card title This Vercel project is not linked to GitHub. "The Vercel project serving this domain is not connected to a GitHub repository, so Ulika cannot preview a branch on it." In a pre-check: "my-site on Vercel is deployed outside Git, so nothing would ever build a change to example.com." Also called not-git-linked.

Why it happens. The project was deployed with the Vercel CLI or an upload, not from a Git repository.

How to fix it.

  1. Open the link in the message. It opens the project's Connect this site to GitHub page in Ulika.

  2. Click Connect this site to GitHub. This links the Vercel project to the repository Ulika found. Your site keeps running as it is; later pushes deploy it.

  3. Run the connect step again.

If you prefer to do it on Vercel yourself, open the project's Settings > Git and connect the repository.

Retries by itself? No.

vercel-linked-to-other-repository#

What you see. The card title This Vercel project deploys a different repository. "The Vercel project serving this domain deploys a different repository or production branch than the one you selected." In a pre-check: "my-site on Vercel deploys acme/other (main), not acme/site." Also called repo-mismatch.

Why it happens. The Vercel project that serves your domain is built from another repository, or from a production branch that is not your repository's default branch.

How to fix it.

  1. Decide which repository really builds your site.

  2. If Ulika picked the wrong one, choose the right repository in the connect step (or run ulika connect <url> --repo owner/name).

  3. If the Vercel project has the wrong production branch, change it under the project's Settings > Git.

Retries by itself? No.

vercel-project-held-elsewhere#

What you see. If you are a member of the holding workspace: "my-site on Vercel is connected in your workspace “<workspace>”, project “<project>”. Switch to that workspace in Ulika (or sign in with the account that owns it), delete the project, then run again." Only the direct answer to ulika connect <url> --check names the workspace, and only to its members; anything a batch stores says instead: "This Vercel project is connected to another Ulika workspace you are not a member of. If it is yours, run ulika connect --check <site address> to see which of your workspaces holds it; otherwise ask that workspace's owner." Ulika never names a workspace you are not a member of. Also called project-already-connected.

Why it happens. A Vercel project can belong to one Ulika project at a time. Another workspace's live project holds it, and Ulika never takes it over.

How to fix it. In the other workspace, disconnect the repository or delete the project there, then run again. If the other project is gone (for example it was deleted), Ulika releases the old binding by itself.

Retries by itself? No.

vercel-project-in-use#

What you see. "my-site on Vercel is already used by another project in this workspace (other.com)". The fix is Open that project and disconnect it first.

Why it happens. A different Ulika project in the same workspace, serving a different real domain, is bound to this Vercel project (for example one repository serving two sites).

How to fix it. Open the named project and disconnect it, or connect your site to a different Vercel project.

Retries by itself? No.

address-on-platform-host#

What you see. A warning: "my-site also answers on example.com. Ulika keeps the address you gave (my-site.vercel.app); give example.com instead if that is the site's real address."

Why it happens. You gave the project's vercel.app address, but it also has a real domain.

How to fix it. Use the real domain: ulika connect https://example.com. Not blocking.

Retries by itself? Not applicable.

no-permission#

What you see. The card title This token cannot reach the project. "That Vercel access is missing a permission Ulika needs. Use a token from the team that owns the project, with access to it." In a step: "Vercel refused this change to the build token variable: the connected access cannot manage it."

Why it happens. The token is valid but belongs to an account or team without access to the project, or it lacks permission to change environment variables or hooks.

How to fix it. Create a token from the team that owns the project (as an owner or a member who can manage it), scoped to that team, and connect again.

Retries by itself? No.

Problems while preparing the project#

ENV_CONFLICT#

What you see. In the failure details: POST /v10/projects/.../env -> 400 ENV_CONFLICT (or ENV_ALREADY_EXISTS). The explanation reads "Vercel says the build token variable already exists on the project but will not let Ulika see or change it (it may be shared from the team's settings)." A pre-check may show the warning below as legacy-token-variable.

Why it happens. Ulika puts a build token on your project in a variable called ULIKA_BUILD_TOKEN. That name is already taken by a variable Ulika is not allowed to change. The usual cause is an earlier install of the CLI that created it with your own token, a variable shared from your team's settings, or leftover copies limited to a single branch.

What Ulika does by itself. It does not fight the existing variable. When the old name is held by something it cannot change, it stores its token under its own name, ULIKA_CONNECTOR_TOKEN, which the build reads first, and leaves the old variable alone. You only see an error when Ulika cannot do even that, or when a duplicate it must remove is refused.

How to fix it.

  1. On Vercel, open the project and go to Settings > Environment Variables.

  2. Look for variables named ULIKA_BUILD_TOKEN and ULIKA_CONNECTOR_TOKEN.

  3. If one of them is a shared variable linked from the team, unlink it from this project (or delete it from the team's shared variables if nothing else needs it).

  4. Delete extra copies that are limited to a single branch. Ulika needs one variable that applies to Production and Preview.

  5. Run the connect step again.

Retries by itself? No. Vercel refused it; asking again gets the same answer.

legacy-token-variable#

What you see. A warning: "my-site has a ULIKA_BUILD_TOKEN variable that another tool created (usually an earlier CLI install) and Ulika is not allowed to change. It is left alone: Ulika stores its own token as ULIKA_CONNECTOR_TOKEN, which the site's build reads first."

Why it happens. See ENV_CONFLICT. This is Ulika working around it, not an error.

How to fix it. Nothing is required. You can delete the old ULIKA_BUILD_TOKEN variable in the project's environment variables whenever convenient.

Retries by itself? Not applicable.

unseen-deploy-hooks#

What you see. A warning: "Vercel does not show my-site's deploy hooks to Ulika, so Ulika cannot tell which ones are its own. Earlier runs may have left duplicates named "Ulika <project>". Nothing is blocked."

Why it happens. Vercel hides deploy hooks from integrations, so Ulika cannot list them.

How to fix it. Nothing, unless you want to tidy up: open the project's Settings > Git > Deploy Hooks and delete extras named Ulika ... that you no longer need. Do not delete the current one if the site fetches content at build time.

Retries by itself? Not applicable.

previews-protected#

What you see. A warning: "Vercel Authentication protects my-site's previews, so Ulika cannot read them directly. Ulika tries to add a Protection Bypass for Automation secret ...; if Vercel refuses, it verifies the preview through Vercel's own deployment status instead." If Vercel refuses outright, the sentence ends "Nothing is blocked". In a connect run that waits more than about three minutes, you get the attention reason preview-protected.

Why it happens. Your previews sit behind Vercel Authentication or a password, so Ulika cannot fetch the preview to confirm the connector. Vercel only lets its native integrations create the automation bypass, so Ulika's integration is often refused.

How to fix it.

  1. If the build is still running, wait; Ulika keeps checking Vercel's deployment status.

  2. Open the deployment in Vercel. If the build failed, fix it. If it is ready, run the command again.

  3. To let Ulika read previews directly, open the project's Settings > Deployment Protection and turn off Vercel Authentication for previews.

You can also click Activate yourself: Ulika merges, checks your live site, and undoes the change if the live build fails.

Retries by itself? For about three minutes, yes. Then it waits for you.

release-incomplete#

What you see. "Ulika could not remove everything it created for a previous project on this Vercel project (...). It kept that project's record so the next run retries."

Why it happens. A project that used this Vercel project before was deleted, and some of its items (a variable, a hook, a webhook or a secret) could not be removed.

How to fix it. Run the step again; Ulika retries. If it repeats, open the Vercel project and remove items named ULIKA_... or Ulika <project> that belong to the deleted project.

Retries by itself? Yes.

did-not-converge#

What you see. "Ulika changed ... but it still does not match what was asked: ...".

Why it happens. Ulika verifies after every change. Something it just changed reads back differently. It can happen if something else changes the same setting at the same time.

How to fix it. Make sure no other automation edits the project's Ulika variables, then run the step again.

Retries by itself? No.

busy#

What you see. "Another run is already connecting this site. Ulika will try again shortly."

Why it happens. Two runs for the same site or Vercel project overlapped. Ulika serialises them.

How to fix it. Wait. It continues by itself.

Retries by itself? Yes.

Preview and publishing problems#

Project deleted on Vercel#

What you see. "Vercel does not know the project: it may have been renamed, moved to another team or deleted." The project's reason shows as project-not-found.

Why it happens. The Vercel project Ulika recorded is gone.

How to fix it. If it was renamed or moved, reconnect Vercel with access to the new location. If it was deleted, recreate the project on Vercel, link it to your repository, and connect again. Ulika's own items on a deleted project disappear with it.

Retries by itself? No.

Deploy hook errors when you publish#

For sites that fetch content when Vercel builds (older connections), Publish asks Vercel to rebuild through a deploy hook. You may see:

  • "This project has no deployment connection." The deploy hook was never created or was removed. Reconnect Vercel so Ulika can create the hook again.

  • "Invalid deployment connection." The saved hook is not an https://api.vercel.com address, so Ulika refuses to call it. Reconnect Vercel so Ulika can create it again.

  • "Vercel returned 500. Publication is unconfirmed; drafts remain saved. Retry after 15 minutes." Vercel answered with an error (the number varies). The rebuild may or may not have started. Your drafts are safe; Ulika keeps checking the live site and you can retry later.

  • "Vercel did not confirm the request. Publication is still being checked; drafts remain saved. Retry after 15 minutes." The request timed out. Same advice.

  • "The deployment is not confirmed live yet. Reopen Publish to retry the same saved release." The release is saved but your live site has not served it yet. Reopen Publish to retry the same release.

  • The connector notice Deploy hook missing: the connector is active but Ulika could not set up the hook, so published content will not go live until one exists.

Sites that publish through Git (new connections) do not use a deploy hook; a Publish commits one file and Vercel builds it. See Publishing and Failed builds.

Disconnecting Vercel#

Click Disconnect Vercel on the connect card. Ulika removes only what it recorded creating: the build token variable, the deploy hook, the webhook and the protection bypass secret, and uninstalls its integration when you connected that way. It then shows Disconnected <account>. Removed N items Ulika had added to your Vercel projects.

If something could not be removed, you see "These could not be removed and are still on your Vercel account" with a list (build token variable, deploy hook, webhook, protection bypass secret or Ulika integration). Remove them in the project's Vercel settings. For a pasted token, the token itself still works until you revoke it on Vercel's token page.

Was this page helpful?

PreviousNeeds attention reasonsNext GitHub problems

On this page

  • Before you start
  • Connecting Vercel
  • not-configured
  • not-connected
  • token-invalid
  • team-not-found
  • state-invalid
  • rate-limited
  • unavailable
  • unexpected-response
  • request-rejected
  • Project problems
  • vercel-project-not-found
  • host-not-on-vercel
  • vercel-not-git-linked
  • vercel-linked-to-other-repository
  • vercel-project-held-elsewhere
  • vercel-project-in-use
  • address-on-platform-host
  • no-permission
  • Problems while preparing the project
  • ENV_CONFLICT
  • legacy-token-variable
  • unseen-deploy-hooks
  • previews-protected
  • release-incomplete
  • did-not-converge
  • busy
  • Preview and publishing problems
  • Project deleted on Vercel
  • Deploy hook errors when you publish
  • Disconnecting Vercel
Ulika documentationFAQ · CLI reference · Terms · Privacy