Troubleshooting: Connection & Server

Use this page if Ziva cannot connect, its background service will not start, or you cannot sign in. See the main troubleshooting page for how to find and export logs.

“Ziva’s background service didn’t start”

A message starting with Ziva’s background service means the local Ziva server didn’t start up successfully. The message names the most likely cause, such as another Godot editor holding the port, antivirus software, or a firewall or VPN.

1. Follow the fix in the message, then click Retry.
2. Restart Godot.
3. Check the port / firewall section below.
4. If it persists, export your logs before trying a reset. Resetting removes this project’s Ziva chats and settings.

“Disconnected” banner or a reconnecting overlay

If Ziva shows a disconnected banner or an Unable to Reconnect overlay saying Could not reach the plugin server, its local connection has been lost.

• Wait briefly for Ziva to reconnect automatically.
• If the overlay stays up, click Retry if offered, then restart Godot.
• If it keeps dropping, check the port / firewall advice below.

An interrupted response after a restart

If a response says resumable history is unavailable, you can still read its saved content, but Ziva cannot resume that response automatically.

1. Choose Retry for the original request if offered. This sends a new model request.
2. If Retry is unavailable or says history is missing, start a new chat and resend the original request with any details it needs.
3. Do not delete project data to clear the message. Reconnecting cannot recover the missing history.

For read-only chats, see Chat history. Before restoring project files, check the limits and manual-work warning in Undo and checkpoints.

Repeated “Connection lost. Retrying…” at attempt 1/6

• Keep Godot open and wait for the current task to resume. Do not resend the same request while it is still running.
• If the message keeps appearing while tasks still run, update Ziva.
• If it persists, restart Godot and send a bug report with the logs. Do not reset or delete your chats just to clear this message.

Blocked ports or firewall

Ziva’s background service connects to the panel on your own computer using a free port in the 7012-7041 range. For this connection, a firewall only needs to allow Godot to communicate locally.

• If a corporate firewall, VPN, or security tool blocks this local connection, the server can’t be reached. Add an exception for Godot, or temporarily disable the tool to confirm it’s the cause.
• If lots of other apps are running, restarting your machine frees things up; Ziva picks a free spot automatically.

Can’t reach Ziva from Spain during football matches

During LaLiga matches, some Spanish internet providers (notably Movistar) block shared Cloudflare addresses under court orders. Ziva runs on Cloudflare, so the website and the Godot panel can stop connecting until the match ends, along with many other websites. Your account and projects are not affected.

• Try again after the match. The block lifts on its own.
• Use mobile data or another network.
• Use a free VPN such as Cloudflare WARP (https://one.one.one.one ).

Can’t log in

Signing in opens your browser; once you’re signed in there, the editor connects on its own.

• If no browser opened, copy the login link Ziva shows and open it manually.
• Make sure you finish signing in before the link expires. If it times out, start the login again.
• Behind a proxy or firewall, the sign-in step can be blocked. Confirm you can reach the Ziva website in a normal browser on the same machine.

Login problems after a reset or update

If you switched accounts or updated and now see sign-in errors, you may have an old, expired sign-in saved. Open Settings → Account, click Log out, then sign in again. Resetting Ziva does not clear your sign-in.