> For the complete documentation index, see [llms.txt](https://enercalc.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://enercalc.com/docs/sel-faq/setup-and-licensing/it-administration/network-requirements/network-requirements-cloud-enercalc.md).

# Firewall Requirements - cloud.enercalc.com

Firewall Requirements for ENERCALC Cloud (Dizzion Frame)

ENERCALC Cloud streams to your users through Dizzion Frame. To make it work through your firewall, allow the **outbound** traffic below from user devices. Users' devices start every connection, so a stateful firewall needs **no inbound rules**.

### Summary

| # | Purpose                                 | Protocol / Port                       | Destination            |
| - | --------------------------------------- | ------------------------------------- | ---------------------- |
| 1 | Sign-in, session control, web UI        | **TCP 443** (HTTPS and WebSocket/WSS) | Hostnames listed below |
| 2 | Desktop/app streaming (FRP8), preferred | **UDP 4503-4509**                     | Any (see note)         |
| 3 | Desktop/app streaming (FRP8), fallback  | **TCP 4503-4509**                     | Any (see note)         |

> **Note on rules 2 and 3:** Each session runs on a streaming server whose IP address is assigned dynamically and changes between sessions. You cannot pin these rules to fixed IPs. Allow the port range to any destination.

> **UDP is preferred; TCP is the fallback.** FRP8, Frame's streaming protocol, uses UDP by default. If a UDP connection can't be made when a session starts, it falls back to TCP on the same ports. Open both. Dizzion's documentation describes the fallback only at session start, not partway through a session.

### Rule 1: TCP 443 hostnames

Allow outbound TCP 443 (including WebSocket/WSS upgrades) to:

```
  use.difr.com
  api.use.difr.com
  img.use.difr.com
  assets.use.difr.com
  login.use.difr.com
  logging.use.difr.com
  downloads.difr.com
  console.nutanix.com
  img.frame.nutanix.com
  img.console.nutanix.com
  cpanel-backend.console.nutanix.com
  terminal-prod.frame.nutanix.com
  logging.console.nutanix.com
  login.console.nutanix.com
  messaging.console.nutanix.com
```

**If your firewall supports wildcards,** these four entries cover the whole list:

```
  *.difr.com
  console.nutanix.com
  *.console.nutanix.com
  *.frame.nutanix.com
```

> **Allow both the difr.com and nutanix.com domains.** Dizzion is moving from `*.nutanix.com` to `*.difr.com`. Until that move is finished, both sets must be reachable. Do not remove the nutanix.com entries.

> **SAML / SSO administrators:** Allow the new `img.*.difr.com` domains, but do **not** change SAML 2.0 settings to use them. Keep using `img.console.nutanix.com` and `img.frame.nutanix.com` until Dizzion says otherwise.

### Rules 2 and 3: Streaming ports

Allow outbound to any destination:

* **UDP 4503-4509** (preferred)
* **TCP 4503-4509** (fallback)

### Not required

* No inbound ports or port forwarding.
* No FRP7 ports. FRP7 reached end-of-life on June 30, 2024. Only FRP8 is used.

### Sources

Dizzion Frame Platform Administrator's Guide, "Public Networking (Public Cloud)": <https://docs.difr.com/books/platform-administrators-guide/page/public-networking-public-cloud>

Dizzion FAQ, "Does Dizzion use Microsoft RDP or another 3rd party protocol?" (UDP default, TCP fallback): <https://docs.difr.com/books/faq-daas-cloud-pc/page/does-dizzion-use-microsoft-rdp-or-another-3rd-party-protocol>


---

# 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://enercalc.com/docs/sel-faq/setup-and-licensing/it-administration/network-requirements/network-requirements-cloud-enercalc.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.
