Troubleshooting

The CLI checks your own computer before sharing. Start your dev server (for example npm run dev), wait until it says it's ready, and check that http://localhost:5173 opens in your browser. Then run the share command again.

Use the port your dev server prints, not the framework's usual one: it changes when the default is busy. Vite might print Local: http://localhost:5174/ — then share 5174.

CLI logins last 90 days and can be revoked in Settings → CLI. The share command starts a new sign-in automatically: approve it in your browser and sharing continues.

• Open the link the CLI printed, check that the code matches your terminal, and click Authorize CLI.
• Make sure you're signed in to the right Localians account in that browser.
• The request expires after 10 minutes. Run the command again for a fresh code.
• No browser opened? Copy the printed link into one yourself.

• “This preview link isn't active” — sharing stopped (Ctrl+C, Stop Sharing, logout or the 24-hour limit). Run the share command again; you'll get a new link.
• “The app isn't running” — the link works, but your dev server stopped or crashed. Restart it; the same link starts working again.
• The address can't be found — during the beta, links on the local test server (*.preview.localhost) only open on the computer running it. Public links need the Localians service to be deployed.

• The project is password protected. Send your client the password (separately from the link).
• Forgot it? Set a new one on the project page under Preview access. Everyone, including you, enters the new one.
• After several wrong tries, that visitor has to wait a few minutes. To make the preview public instead, choose Public in Preview access.

Commands copied from Share App include a one-time code that works once, within 30 minutes. Reload the Share App page and copy the new command — or run localians share <port> without --setup.

The share command connected, but Localians couldn't yet confirm who may open the preview, so it stays closed rather than risk being public. It clears within about 20 seconds; if it doesn't, the Localians service may be having trouble — try again shortly.

Stop a preview you no longer need, or wait until the daily bandwidth limit resets at midnight UTC. The limits keep the service fast and prevent abuse.

Your computer's connection to Localians dropped (sleep, Wi-Fi change, VPN switch). The CLI reconnects by itself and keeps the same link while it can. If it keeps failing, check your internet connection, then stop and restart the share command.

• Reconnecting — the share command is trying to reconnect. Make sure it's still running and your computer is awake.
• Disconnected / Revoked / Expired — that share has ended for good and its link won't come back. Share again for a new link.

Next.js needs your preview domain in allowedDevOrigins (see the Next.js guide). For other frameworks, check that you didn't pass --host-header preserve without allowing the preview host.

The CLI only makes outgoing HTTPS connections — you never need to open ports on your router. Some company networks, proxies or VPNs block the long-lived connection it uses. Try another network or disconnect the VPN; if that fixes it, ask your network admin to allow outgoing HTTPS (including WebSocket-style upgrades) to the Localians servers.

The package isn't published to npm during the beta, so npx localians can't work yet. Install the beta from a Localians checkout (see the CLI guide). If localians still isn't found after npm link, make sure npm's global folder is on your PATH:

This only happens when the Localians server runs on your own machine with its development certificate. Trust the development CA (see CLI guide → certificates) instead of clicking through warnings. Real deployments use publicly trusted certificates.