When a network blocks Turn Zero #

View this page as Markdown

On this page

Prompt:

My app loads at home but not on the office Wi-Fi. Is the platform down, or is it the network?

Also works:

  • "A tester says the sign-in page never opens for them."
  • "Your MCP server stopped connecting when I moved to the café."

Compare DNS lookups through the affected network and a public resolver, then test the site from another network. This helps distinguish DNS filtering from an application or platform outage. If a network policy blocks the domain, ask its administrator to allow it.

What your AI tool does #

  • Looks up the same name twice from your computer in the Domain Name System (DNS), which turns names into addresses. One lookup goes through the network's own resolver, the other through a public resolver over HTTPS. Then it compares the two answers.
  • Calls read_status with the application's identifier to read the application's state, if it can reach the platform.
  • Drafts a request to the network's administrator that lists the domains to allow.
  • Changes no setting on your computer or the network. It asks where the problem happens and, if possible, asks you to try the same checks from another network.

What you need #

  • A computer on the network that has the problem, so the checks can run there. If your AI tool runs elsewhere, give these checks to the person on the affected network and ask them to send back the results.
  • If possible, a second network to compare against, such as your phone's mobile data.

Before your AI starts #

For the AI tool: Check the following before starting.

  • For an application, use the production hostname, <label>.ai.host, or development hostname, <label>-dev.ai.host, from the address that failed. If the platform is reachable, list_applications returns the label.
  • For a failed MCP connection, use the hostname in the connection's configured URL. You need neither an application label nor a working tool call to begin these checks.

Steps #

The platform uses turnzero.ai and its subdomains for the site, documentation, sign-in, developer tools and platform routes. MCP connections use turnzero.ai, tzcloud.turnzero.ai or tztools.turnzero.ai, as Connect your AI assistant describes. ai.host serves every application at <label>.ai.host and <label>-dev.ai.host, including the sign-in pages for its end users.

Some networks run a filter that blocks names by category. When you look up a blocked domain, the filter answers with a name that belongs to its vendor, or with nothing. Your browser then says the site cannot be reached.

On public Wi-Fi, first finish the network's sign-in or terms page, if one is offered, and retry the address. Ask the venue's staff for help finding that page; do not bypass a certificate warning to reach it.

1. Run the two lookups #

Ask the network's resolver first. Then ask a public resolver over HTTPS, which goes around the network's resolver.

nslookup <label>.ai.host
curl -s -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=<label>.ai.host&type=A"

In Windows PowerShell, run the same two lookups like this.

Resolve-DnsName <label>.ai.host
curl.exe -s -H "accept: application/dns-json" "https://cloudflare-dns.com/dns-query?name=<label>.ai.host&type=A"

To check the platform itself, run both lookups again with turnzero.ai as the name. For an MCP connection, repeat them with the hostname in its configured URL too.

If the lookup over HTTPS also fails, report that this comparison is unavailable. Keep its error and try the same checks from the second network, if available. Do not change the computer's DNS settings or disable a filter to make the comparison work.

2. Read the responses #

If both lookups resolve the name, DNS filtering is less likely; the network could still block HTTPS traffic. Compare access from another network. If the platform is reachable, check the application with read_status. Check the platform's public health route without a credential:

curl -i https://turnzero.ai/healthz

In Windows PowerShell:

curl.exe -i https://turnzero.ai/healthz

Expect HTTP 200 and a JSON body with "ok": true, contract_version and build. This checks the platform route; it does not establish that the application or every platform service is healthy.

After changing networks, retry the failed MCP call through the existing connection with the same configured URL. If it connects, use the connection check in Connect your AI assistant: call start and check that the hosting tools are available. A network change alone calls for neither reinstalling the connection nor signing in again. If the retry returns a sign-in error, follow that error's remedy on the connection page.

If the network's resolver returns a filter vendor's block-page address or no answer while the public resolver succeeds, DNS filtering is a possible cause. Look for a vendor named on the block page, or ask the network administrator to identify the returned hostname or address. A different IP address alone does not identify a vendor. DNS results alone do not prove the application is healthy. Confirm access from another network and give both results to the network administrator.

A certificate error such as NET::ERR_CERT_AUTHORITY_INVALID can indicate HTTPS inspection or a certificate configuration problem. Record the certificate's subject and issuer in the browser, the requested hostname and the error. Compare the same address from the second network, if available, and give the results to the network administrator.

If HTTPS inspection is responsible, ask for the affected hostnames to be exempted from inspection as well as allowed by the DNS and URL filter. Do not bypass the warning or install a certificate to make the check pass. After the administrator's change, retry the same address on the affected network; it should open without a certificate warning.

3. Ask the network's administrator #

Only the administrator can change what the network allows. On a public network, ask the venue's staff to pass the request to whoever manages its Wi-Fi. Send them the two domains and what each one is for.

Please allow turnzero.ai and ai.host, with every name under both domains, in the network's DNS and URL filter.
turnzero.ai is the Turn Zero Cloud platform: its site, documentation, sign-in, and developer tools.
ai.host is where applications built on Turn Zero Cloud are served, each at its own name under ai.host.
Opening https://ai.host shows a page that describes the domain and who operates it.

A filter usually blocks a domain by the category its vendor gave it, such as newly registered or insufficient-content. The administrator can add the two domains to the allow list. Or they can ask the vendor to correct the category, which only the vendor's customer can do. A vendor's crawler, a program that visits and reads sites, helps it sort them. A production application whose first page describes it in plain text gives the crawler something to read.

Every application has a name under ai.host. Any application can also answer at a custom domain (Attach your own domain). A filter judges that domain by its own category.

Expected result #

A response naming a filtering vendor, or a failed local lookup when the HTTPS lookup succeeds, suggests DNS filtering. Different answers alone do not prove it: resolver caches and geographic routing can also differ. Matching answers do not rule out filtering of HTTPS traffic.

read_status returns the application's state and each environment's deployed version.

Refusals #

See the refusals reference for other platform errors.

Refusal Status Cause Remedy
unknown_application 404 An HTTP request to the application's hostname reached the router, but no live application has that label, or its owner record is missing. This is not a DNS response or a read_status refusal. Use the application's current hostname from list_applications. After a rename, allow the router's bounded update interval before retrying. A deleted application's hostname is not reused; if its owner account was deleted, the caller cannot repair that.
no_such_application 404 read_status named an application that your account does not have. Use the identifier list_applications returns.
application_other_account 403 application names an application that another account holds, not the account the call is signed in as. The detail names the account the call acted as, and says nothing about the other one. Compare turnzero whoami with read_account over your AI tool's connection. The two may be signed in to different accounts. Make the call from the one signed in to the account that holds the application.