Skip to main content
Occasionally, you may run into issues installing the Gorelo Agent. Here are a few things to consider.

Supported operating systems

Gorelo only supports operating systems that their vendor (Microsoft or Apple) still supports.

Prerequisite check

Gorelo provides a prerequisite check for Windows and macOS. It confirms the device meets the requirements and can reach Gorelo’s services, and ends with a clear PASS or FAIL. Both scripts ask you to choose your Gorelo region: USW (United States West) or AUE (Australia East). They then check the matching Gorelo servers, IoT Hub, and download source for that region. When you run a script interactively, it prompts you to pick a region. To skip the prompt, for example in unattended runs, set the GORELO_REGION environment variable to USW or AUE beforehand.
  1. Open an elevated PowerShell window on the computer experiencing agent issues.
  2. Copy the entire script below, paste it into the window, and press Enter:
gorelo-check-windows.ps1
  1. Choose your region (USW or AUE) when prompted.
  2. Resolve any failures using the table below, and make sure your fixes persist across PowerShell sessions and reboots.
The script also checks DNS resolution for the region’s IoT Hub (gorelo.azure-devices.net for USW, gorelo-aue.azure-devices.net for AUE). If the IoT Hub doesn’t resolve, the script shows a warning, not a failure. The warning doesn’t block the installer check from passing, but the agent might fail to connect after install, so it’s worth fixing.

Agent installed but asset shows offline

An asset’s online or offline status in Gorelo comes from the Gorelo Agent. Gorelo Connect is a separate remote control component. Gorelo Connect can run, and you can start remote sessions, while the Gorelo Agent can’t reach Gorelo’s cloud. See Gorelo Agent vs. Gorelo Connect. If the Gorelo Agent is installed but the asset shows offline in the asset list:
  1. Run the prerequisite check on the affected device.
  2. Review the URL checks for the Gorelo gateway, API, and hub servers. A failure means a firewall, proxy, or DNS setting blocks the Gorelo Agent.
  3. Review the IoT Hub DNS warning. The Gorelo Agent can fail to connect if the device can’t resolve gorelo.azure-devices.net (USW) or gorelo-aue.azure-devices.net (AUE), even when other internet traffic and Gorelo Connect work.
  4. Review the time synchronization check. Fix any time mismatch.
  5. Check the Gorelo Agent log for connection errors. See Logs for the Agent log location on Windows and macOS.

Logs

Gorelo logs everything to:
As the install progresses, the installer creates additional folders at each stage with log files inside:InstallerHandler > Installer > Shell > AgentThe most common issues appear in the following logs:
If Gorelo support asks for log files, send the entire LogFiles folder as a .zip.

Still having problems?

If you’re still experiencing installation or connection issues after resolving all failures in the Gorelo Agent Check, contact Gorelo support directly. Use the support chat via the ”?” icon in the bottom-left menu.