ekkoboard docs

Fixing AI connection issues caused by DNS filters, VPNs, or ad blockers

If EkkoBoard’s AI features stop working while regular keyboard typing still works, a DNS filter, VPN, ad blocker, firewall, or security app may be blocking the connection to our servers.

This can happen with services such as NextDNS, AdGuard, Blokada, or similar filtering tools. Filters configured on your phone can affect both Wi-Fi and mobile data.

Common symptoms

  • Voice typing fails or stays on “processing” without returning text.
  • AI editing or generation does not respond.
  • Regular keyboard typing still works.
  • Clearing the cache or reinstalling EkkoBoard does not help.

These symptoms can have other causes, but the steps below can help you check whether filtering is involved.

Step 1: Check whether a filtering service is involved

If you use a VPN, DNS filter, ad blocker, or security app, temporarily pause its filtering or disconnect it, then try the affected EkkoBoard feature again.

If EkkoBoard works with the service disabled, turn it back on and follow the steps below to add an exception.

Step 2: Allow EkkoBoard’s server connections

Open your filtering service’s settings or online dashboard. Look for a section called Allowlist, Whitelist, Exceptions, or Allowed domains.

Add these hostnames as separate entries:

transcribe-audio-prod-jhhn2jvioa-uc.a.run.app
api.ekkoboard.com

Enter only the hostnames, without https://, spaces, or a trailing slash.

The first hostname is our current transcription server. The second is the API address we plan to use in the future. Adding both prepares your configuration for that change.

For NextDNS, visit my.nextdns.io, select the configuration used by your phone, and open Allowlist.

Other services may use different settings. If yours only offers exceptions by app, look for an option to exclude EkkoBoard from filtering or use split tunneling.

Step 3: Test again

With your VPN or filtering service enabled, try the affected EkkoBoard feature again.

If it still fails, restart your phone and retry. This can help clear cached DNS results.

Only allow the specific hostnames listed above. You do not need to allow the entire run.app domain.

Still having trouble?

If your filtering service provides connection logs, check them immediately after a failed attempt. Look for blocked requests associated with EkkoBoard and note the hostname and blocking reason. Additional hostnames may need investigation if other AI features remain affected.

Then save an EkkoBoard diagnostic log:

  1. Try the affected AI feature again.
  2. Immediately after it fails, open EkkoBoard → Settings → About → Save log.
  3. Contact EkkoBoard support through our website and include:
    • The saved log file.
    • Your phone model and EkkoBoard version.
    • The name of your VPN, DNS filter, ad blocker, or security app.
    • Whether temporarily disabling it resolves the issue.
    • Any relevant blocking details or screenshots.

Please crop unrelated browsing activity or personal information out of screenshots.

If the filter is managed by your workplace, school, or network administrator, ask them to review the blocked connection and add the appropriate exceptions.