> For the complete documentation index, see [llms.txt](https://learn.doubletick.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://learn.doubletick.io/troubleshoot-errors/troubleshoot-common-whatsapp-api-errors/how-to-fix-the-failed-to-fetch-error.md).

# How to fix the "Failed to fetch" error

Learn how to fix the "Failed to fetch" error on the DoubleTick login page, including the domains and IP addresses your IT team needs to allowlist.

The **"Failed to fetch"** error usually means your browser or device cannot establish a **secure connection** with DoubleTick servers. In most cases, the fix is a quick change to your network, browser or device settings. This guide walks you through each fix, starting with the one that solves it most often.

#### What's covered

* [Why does the "Failed to fetch" error happen?](#why-does-the-failed-to-fetch-error-happen)
* [How to allowlist the required domains and IP addresses](#how-to-allowlist-the-required-domains-and-ip-addresses)
* [How to fix the error from your network, browser and device](#how-to-fix-the-error-from-your-network-browser-and-device)
* [Key takeaways](#key-takeaways)

#### Why does the "Failed to fetch" error happen?

The most common causes are:

* Network, firewall or proxy restrictions
* VPN or antivirus interference
* Browser CORS or security blocking
* SSL inspection or DPI (Deep Packet Inspection)

#### How to allowlist the required domains and IP addresses

Make sure the following domains and IP addresses are **allowlisted** by your network firewall, antivirus, proxy server or VPN.

**Core DoubleTick services:**

* `https://doubletick.io/`
* `https://api.doubletickapi.com/`
* `https://mini.doubletick.io/`
* `https://ad-insight.doubletick.io/`

**Product analytics and logging:**

* `https://q.clarity.ms/collect`
* `https://eu.i.posthog.com/`

**Platform integrations:**

* `https://api.canny.io/api/`

**Google identity and authentication:**

* `https://securetoken.googleapis.com/`
* `https://identitytoolkit.googleapis.com/`

**Additional required domains:**

* `doubletick.io`
* `*.doubletick.io`
* `bothook.io`
* `*.bothook.io`
* `*.wmeta.me`
* `wmeta.me`
* `getsmsotp.com`

{% hint style="info" %}
Add both the root domains and the wildcard versions. Various sub-services may resolve dynamically.
{% endhint %}

**DoubleTick IP addresses:** Along with the domains, some networks also need these IP addresses to be **allowlisted** before the login page can connect.

* `3.6.248.161`
* `43.205.183.91`
* `13.235.150.127`
* `65.1.9.106`

**What your IT team needs to do**

* **Allowlist** all of the URLs, domains and IP addresses above.
* Make sure **ports 443 (HTTPS) and 80 (HTTP)** are open.
* If you use **SSL inspection or DPI (Deep Packet Inspection)**, disable it for the domains above.

#### How to fix the error from your network, browser and device

If the domains and IP addresses are already allowlisted, or you can't change your network settings, try these fixes in order.

* **Check your internet network:** If you're on a corporate or restricted Wi-Fi, switch to a mobile hotspot or an open network. Turn off your VPN if it's active. You can also check whether other team members can access [web.doubletick.io](https://web.doubletick.io/).
* **Clear your browser cache and cookies:** Corrupted browser data may block key scripts from loading. Go to your browser settings, open **Privacy & Security**, and click **Clear browsing data**. Select **Cookies and Cached Files**, then refresh the DoubleTick login page or restart your browser.
* **Try an incognito window or a different browser:** Sometimes browser extensions or cache can interfere. Open an incognito or private window and try logging in. You can also use another browser, such as Chrome, Firefox or Edge. Make sure JavaScript is enabled.
* **Check the time and date on your device:** An incorrect system time can block secure connections. Open your device settings and set the time and date to automatic, or sync it with the internet. Then refresh and try again.
* **Disable your antivirus or firewall temporarily, if it's safe to do so:** Security tools like Kaspersky, Norton or enterprise software may silently block background scripts. Disable the antivirus or firewall temporarily and try logging in. If it works, add the DoubleTick URLs to the tool's safe list, and then turn your protection back on.
* **Try these steps on mobile devices:** If you're on iOS or Android, update your browser, restart your phone or switch networks, and make sure app permissions are granted.
* **Check the browser console for errors (advanced):** Open Chrome, right-click the page and click **Inspect**, then go to the **Console** tab. Refresh the page and note any red error messages. You can send screenshots of these errors to <support@doubletick.io> for further help.

#### Key takeaways

* The **"Failed to fetch"** error usually means your browser or device cannot connect securely to DoubleTick servers.
* Ask your IT team to **allowlist** the required domains and the four DoubleTick IP addresses.
* Keep **ports 443 and 80** open. Turn off **SSL inspection or DPI** for DoubleTick domains.
* If you cannot change network settings, try a different network, a cleared cache, an incognito window or another browser.
* Share screenshots of any console errors with **<support@doubletick.io>** if the problem continues.

#### Frequently asked questions

<details>

<summary>Which IP addresses should I allowlist for DoubleTick?</summary>

Allowlist 3.6.248.161, 43.205.183.91, 13.235.150.127 and 65.1.9.106, along with the domains listed in this article.

</details>

<details>

<summary>Do I need to allowlist both domains and IP addresses?</summary>

Yes. Allowlisting the domains is the first step, and some networks also need the IP addresses allowlisted before the login page can connect.

</details>

<details>

<summary>Which ports should be open?</summary>

Ports 443 (HTTPS) and 80 (HTTP).

</details>

<details>

<summary>I still see the error after allowlisting. What should I do?</summary>

Try a different network, clear your browser cache and cookies, or use an incognito window. If it still doesn't work, send screenshots of the errors in your browser console to <support@doubletick.io>.

</details>

#### Related articles

{% content-ref url="/spaces/53n17VnOICC1LtDqlENV/pages/9PNWEnLYMG6AfAKneInP" %}
[WhatsApp Says “Temporarily Unavailable”?](https://learn.doubletick.io/troubleshoot-errors/troubleshoot-common-whatsapp-api-errors/whatsapp-says-temporarily-unavailable.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://learn.doubletick.io/troubleshoot-errors/troubleshoot-common-whatsapp-api-errors/how-to-fix-the-failed-to-fetch-error.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
