> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-developer-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-developer-guide/faqs/network-faqs.md). # Network FAQs **Do I need to whitelist any domains or IPs to use Netmera?** Not necessarily. Whitelisting is only required in environments with strict firewall, proxy, or outbound traffic restrictions. If your infrastructure has open or permissive network policies, no action is needed. **What services require whitelisting?** Whitelisting may be needed to support the following: * API communication * Push notification delivery * CDN content delivery * Other Netmera-related inbound and outbound connections **Where can I find the current list of domains and IP ranges to whitelist?** Since IP addresses and service endpoints may change over time, the most up-to-date whitelist information should be requested directly from Netmera. Contact your Netmera representative or support team to obtain the current list. **How do I know if whitelisting is causing an issue in my environment?** If your organization enforces strict network controls and Netmera services are not functioning as expected such as push notifications not being delivered, API calls failing, or content not loading -a missing whitelist entry is a likely cause. Reach out to Netmera support with your network configuration details for assistance. **What happens if an event cannot be delivered?** The SDK retries events after a timeout, connection failure, or `5xx` response. It uses a backoff schedule of 1, 3, 9, 27, and 81 minutes. The SDK does not retry `4xx` responses. It drops those events immediately because the request cannot succeed without a change. After the fifth attempt, iOS permanently removes the event. Android stops its retry scheduler, so the event can remain in the local queue. --- # 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://user.netmera.com/netmera-developer-guide/faqs/network-faqs.md?ask=&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.