Assistant: Recurrent "Network error"

mmartinortiz

Normally, I get many "type error: network error" messages while using the assistant, not matter what model I use. Refreshing the answer also use to drive to the same error. Eventually, the answer goes through and is fully rendered.

Browser: Brave
System: Linux

The expected behaviour is to not get the "type error"

Thibaultmol

I think I saw someone recently also have problems with brave. Could you try and clear storage/cookies of kagi.com and login again, see if that fixes it?
https://support.brave.com/hc/en-us/articles/360048833872-How-Do-I-Clear-Cookies-And-Site-Data-In-Brave#3

mmartinortiz

Thanks for such quick answer!

I deleted all data and cookies; log in again, open the assistant and continued a previous conversation. I got the same error

What I appreciated, is that the previous message, which also failed, now it was fully rendered.

This is the console output:

Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
/assistant:1 Unchecked runtime.lastError: The message port closed before a response was received.
57ae7ec9-23c4-4c0f-954b-aad6d6e6109e:1 Unchecked runtime.lastError: The message port closed before a response was received.
57ae7ec9-23c4-4c0f-954b-aad6d6e6109e:1 Unchecked runtime.lastError: The message port closed before a response was received.
assistant.bundle.js?v=3a5b6cbb634dca0894857e2c085c35ebcdae34ef:122 PWA install available
/assistant:1 Banner not shown: beforeinstallpromptevent.preventDefault() called. The page must call beforeinstallpromptevent.prompt() to show the banner.
prompt:1
Failed to load resource: net::ERR_CONNECTION_CLOSED

mmartinortiz

What I just noticed, is that if I close the tab and open it again, the content of the message that was reported as "error", now it gets fully rendered.

jogojapan

I had exactly the same issue with a question posed to DeepSeek R1, from the Kagi app on Android, network access through a VPN. But that was the first timeI experienced this.

mmartinortiz

jogojapan

In my case I'm also using a VPN

mmartinortiz

I just tested in the same computer, using the Zen browser. I also get errors:

TypeError: Error in input stream

As with Brave, if I reload the page the assistant's answer is rendered properly.

Thibaultmol

vpn's generally cause problems because Kagi's infra runs on GCP which tends to block vpn traffic;

mmartinortiz

Hi, since I'm experiencing the same issue, I now that no progress was done, but I wonder if you plan to tackle the issue with VPNs at some point in the future.

Thibaultmol

There's not much they can do, it's GCP who's blocking the vpn's, not kagi.