Talivia Docs
Talivia Docs
HomeDashboard
IntroductionInstallationTeamGetting updates
Self-hostingInstall TaliviaUpdatingCustom domainOwner accountLicense and transfersCloudflare and backupsUninstallTroubleshooting
Integrations
AI agents and MCPllms.txtllms-full.txt
Self-hosting

Troubleshooting

Resolve installation, authorization, startup and sign-in problems.

View Markdown

Node.js or npm cannot run the installer

Run node -v. Node.js 22.12 or newer is required. Install a current LTS version from Node.js and open a new terminal if your version is older.

Use the package name exactly:

npx --yes @talivia/lifetime-installer@latest --name talivia

For help or to confirm the installer version:

npx --yes @talivia/lifetime-installer@latest --version
npx --yes @talivia/lifetime-installer@latest --help

Cloudflare authorization fails

Complete authorization in the browser opened by Wrangler, then return to the same terminal. Use the Cloudflare account where the installation should live. The installer requests fresh authorization and does not use an existing local Wrangler login.

For HTTP 403 or Cloudflare 10034, check email verification in your Cloudflare profile. Signing in with Google does not by itself prove that all Workers account setup is complete.

For Cloudflare 10039 while creating the first workers.dev address, open Workers & Pages and complete any required account setup. If Cloudflare restricts the account or shows no available action, request an account review from Cloudflare Support. Repeated installs cannot bypass a Cloudflare account restriction.

The application address is still starting

Keep the installer open while it checks the dashboard and login pages. A new address or certificate may need additional time. When prompted, press Enter to keep waiting in the same terminal.

If the process ended, rerun with the same account, key and Worker name. Existing resources are recovered; do not delete the database to retry. Cloudflare 1102 indicates a Worker CPU limit problem. Check the Worker logs and your Cloudflare plan's limits, or contact support with the error code.

The key already has an active installation

Use the original Cloudflare account and Worker name for an update. To move it elsewhere, issue a replacement key using license transfers.

A setup link has expired or was already used

After setup, sign in through /login on your own application address. If you never completed setup, rerun the installer on the same installation. See Owner account.

Events do not appear

Use the tracking code copied from website settings in your installed dashboard, with that installation's address and website ID. Visit the tracked website once and check its installation status. Review the tracking guide for script and browser checks.

For further help, send the application address, installer version and technical error code to Talivia support. Keep license keys, passwords and Cloudflare tokens out of shared logs.

Uninstall

Remove your own installation and manage the remaining database and license.

Next.js

Install Talivia in a Next.js app with a root layout.