Connect a site
Private previews
How Ulika verifies a connector when your host keeps previews behind a sign-in, including the Vercel protection bypass and its safeguards.
Last updated
Before Ulika puts its connector on your live site, it likes to see the connector working on a preview build of the pull request branch. Many hosts put previews behind a sign-in, such as Vercel Authentication or a password. This page explains what Ulika does when it cannot open your preview, and how to make that smoother.
Why previews matter#
When Ulika opens the connector pull request, your host builds that branch and serves it at a preview address. Ulika then asks the preview for two small files, cms/content.json and cms/code-build.json, and looks for the unique revision id it generated for this connector. If the preview serves that id, Ulika knows the connector is built and working. This check is the only thing that turns a preview into verified. A deploy that simply returned "ok" never counts.
Preview states#
You see these states while connecting. None of the waiting states is a failure.
| What you see | What it means | What to do |
|---|---|---|
| The preview is serving this connector | Verified. Ulika read the revision back off your deployed preview. | Nothing. You can activate. |
| Waiting for the preview | Not confirmed yet. The reason line tells you why (see below). | Wait, or click Check again. |
| Your host built the update, but its preview is private | Your host reported a successful build to GitHub, but the preview asks for a sign-in, so Ulika cannot read the connector. | You can activate. Ulika then checks your live site after merging. |
| Ulika cannot see your host's builds yet | Ulika is not allowed to read your host's build results on GitHub. | Approve Ulika's updated GitHub permissions, or activate with the same post-merge check. |
| The preview build failed | Your host reported that the build failed or was cancelled. Nothing was merged. | Click Open the build log, fix the error, then click Check again. Activate never merges a failed build. |
| Ulika can't see your hosting yet | Ulika has no preview address for this project. | Open the branch and check the preview yourself. You can add a preview address in project settings. |
The reasons shown under Waiting for the preview are:
No deployment of this branch has answered yet. Previews usually take a minute or two.
A deployment answered, but it is not serving this connector yet. It is probably still building.
We could not reach the preview address. It may still be building, or protected.
The preview is private, and your host has not reported a finished build yet.
What Ulika does with a private preview#
Ulika has three ways to deal with a preview it cannot read.
Open it with a bypass (Vercel only, needs the Vercel connection). Ulika can read the preview directly. See below.
Ask your host. Ulika reads the build results your host reports to GitHub. It recognizes a build only when it was reported by the host's own GitHub App (for example Vercel or Netlify). This needs read-only permission for commit statuses, checks and deployments.
Merge on your consent, then prove it on the live site. If your host says the build succeeded but the preview is private, Ulika may merge after showing you this notice inside the approval: "This preview is private, so Ulika can't look at it first. It will check your live site right after you approve, and if the live build fails it undoes its change automatically." Clicking Activate on the live site opens a confirmation that says plainly the preview was not verified and that Ulika reverts the merge if the live build fails; confirming it is the consent. The connector counts as live only once your production site serves its proof.
In every case the same safety net applies: if the production build fails after the merge, Ulika reverts its own change. See Approving a connection for the details and the limits.
The same rule applies when Ulika cannot see your host's builds at all (the GitHub permissions were not accepted): activating means Ulika checks your live site right after merging.
The Vercel protection bypass#
Vercel can put a login wall in front of every preview deployment (Vercel Authentication or a password). To let Ulika read previews, Vercel offers a feature called Protection Bypass for Automation. It is a secret that lets a server skip the wall.
When it connects your Vercel project, Ulika tries to create one such secret with the note Ulika preview verification. Vercel does not always allow this (see "When Vercel will not create one" below). Details:
It is reused. If the stored secret still exists on your Vercel project, Ulika reuses it instead of creating more.
Only Ulika's own secret is ever used. If you made your own bypass secret, Ulika never uses or changes it. It adopts a secret only if its note says Ulika preview verification.
Disconnecting removes it. When you click Disconnect Vercel, Ulika removes a bypass secret it created. It does not remove one you made.
Where the secret may go#
The secret skips protection for every deployment of your project, so Ulika treats it like a password:
It is sent only as the
x-vercel-protection-bypassheader, never in a normal address.It is sent only to hosts that belong to your Vercel project: the deployment addresses Vercel returned for the project, its aliases, and your site's own host.
It is never sent to a
*.vercel.appaddress just because the name ends invercel.app. Anyone can host such an address.It is never sent to an address that came from a GitHub status or check, because anyone with write access to a repository can write those.
It is stored sealed (encrypted) and never shown in the page or sent to the browser.
When Vercel will not create one#
If you connected through the Vercel Integration, Vercel may refuse to let Ulika's integration create a bypass. Ulika then says so and nothing is blocked: it verifies the preview through Vercel's own deployment status and checks the live site on its own domain directly. A connection made with an access token (see Vercel) is the other way to connect.
Making previews easier for Ulika#
You have three choices, from least to most change to your setup:
Do nothing. Ulika uses your host's build report and the post-merge check. This works for most sites.
Approve Ulika's updated GitHub permissions. When the banner Approve Ulika's updated GitHub permissions appears, click Review on GitHub. It lets Ulika read commit statuses, checks and deployments, read-only, so it can confirm a preview without a Vercel connection. See The GitHub App.
Connect Vercel so Ulika can try to create the bypass. See Vercel.
If you want Ulika to read previews directly and are happy for previews to be public, you can also turn off Vercel Authentication for previews in your Vercel project under Settings, then Deployment Protection. That makes previews reachable by anyone who has the address, so only do it if that is acceptable for your site.
Other hosts#
Ulika treats these as a private preview too: a 401 or 403 answer, or a redirect to a sign-in page (Vercel sign-in, a Netlify password page, Cloudflare Access). The bypass secret is a Vercel feature and is never used for other hosts. For them, the options are your host's build report through GitHub, and the post-merge check.
What this means for your site#
Nothing about private previews changes what your visitors see. Your live site keeps serving its previous deployment until a new build succeeds, and the preview check only decides whether Ulika is allowed to merge.
For problems, see Troubleshooting Vercel.
Was this page helpful?