> ## Documentation Index
> Fetch the complete documentation index at: https://kb.reflow.help/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshooting

This guide covers the first things to check when Reflow isn't behaving as expected, along with fixes
for the most common issues integrators run into during setup. If you get stuck or cannot find an
answer here, reach out to us through the live chat on the
[NiagaraMods website](https://niagaramodules.com/contact).

## First Steps

Before digging into a specific issue, work through this checklist:

1. Confirm you've completed the steps in *Installing Reflow in Niagara* to load the modules into
   your platform and the *Quick Start* guide to add the ReflowService to your station.
2. Verify your station platform and web browser meet Reflow's minimum system requirements.
3. If you just installed Reflow and are running into issues, reboot your station before
   troubleshooting further.

## Common Issues

### Reflow Views Are Missing from the Views Menu

The Views menu is available by right-clicking the ReflowService in your station tree and selecting
**Views**, or by double-clicking the ReflowService and using the Views dropdown at the top right.

* **No views available** — If the menu doesn't include the *Content View*, *Config View*, or
  *Redirect View*, your WebService may be disabled or has hit an error that's preventing it from
  starting. See [WebService Issues](#webservice-issues) below.
* **Config View is unavailable** — If the Content View and Redirect View appear but Config View does
  not, the user you're logged in as does not have "write" permission on the ReflowService.

### Reflow Views Are Stuck on a Loading Spinner

Begin by checking whether this happens only in Workbench, or in both a web browser and Workbench.

* **In web browsers and Workbench** — Check your WebService's `X-Frame-Origin` property. It should
  be set to `Sameorigin`, not `Deny`. In Niagara 4.11 and later, `Deny` may be set by default.
* **In Workbench only** — Check your Workbench version. Workbench 4.10.1 has a known issue that
  prevents Reflow from displaying.

### Reflow Views Aren't Displaying Properly in a Web Browser

First, confirm that your [web browser is supported.](/getting-started/requirements)Then, in your
station, go to **Services > UserService** and make sure each Niagara 4 user's **Default Web
Profile** and **Mobile Web Profile** are set to the `HTML5 Hx Profile`.

### Weather and/or Map Views Don't Work in Workbench

Workbench 4.10 and later defaults to having the web browser whitelist turned on. If you want to keep
the whitelist enabled, add Reflow's API servers to the list. The whitelist doesn't affect Reflow
content in a non-Workbench web browser.

See [Web Browser Whitelist](https://docs.reflow.help/core-concepts/workbench#web-browser-whitelist)
for details on configuring your whitelist.

### Licenses Aren't Loading or Refreshing on Embedded Hardware

For licenses to update automatically, the station and platform needs to reach the Reflow licensing
server. Embedded Niagara 4 hardware often doesn't come with DNS settings configured by default — see
[JACE Hardware in the Licensing article](/getting-started/licensing#jace-hardware) for how to add
DNS servers manually.

<h2 id="webservice-issues">
  WebService Issues
</h2>

Reflow's interface is delivered through HTML5 views, which require the station's WebService to be
enabled and running. Confirm that the status is `{ok}` and the JettyWebServer property shows
`(started)`.

* **WebService fails to start**
  * Usually another process on the platform is already using ports 80 and/or 443. This is common on
    demo stations running on a workstation, or on Supervisor stations sharing a Windows or Linux
    server.
  * Go to the station's IP address or hostname in a web browser (prefixed with `http://` or
    `https://`, matching your WebService setup) to identify what's running there. Once you've found
    the conflicting program, shut it down and run the **Restart** action on **WebService >
    JettyWebServer**.
* **Unable to reach the station when WebService is** `{ok}`
  * Confirm you're using the correct protocol. If **Https Enabled** is `true`, ensure that you are
    using `https://`. If **Http Enabled** is `true` and **Https Enabled** is `false`, ensure that
    you are using `http://`instead.

## Licensing Issues

See [Troubleshooting](/getting-started/licensing#troubleshooting) in the Licensing article for
licensing-specific issues, including JACE hardware and outbound firewall configuration.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.