Frequently Asked Questions
General
General
System Overview
Getting Started
Installation
Installation
Steps To Success
Creating Building & Deployment
Installing Onboard's Edge Software
Troubleshooting Installation & Working with IT
Managing Deployments
Data Discovery
Data Discovery
What is BACnet?
Connect Your BACnet Devices
What is Modbus?
Connect Your Modbus Devices
Troubleshooting Discovery
Data Modeling with AI
Data Modeling with AI
What is Staging?
Getting Started with Staging
What is an Ontology?
Onboard's Data Model
Data Modeling with AI
Modeling Points
Modeling Equipment
Modeling Locations
Modeling Relationships
Publish-Unpublish Workflow
Bulk Actions
Renaming Equipment
Deleting Equipment
Reviewing Points Selection for Equipment
Status Tracker
Feature Guides
Feature Guides
Exporting Data (CSV, JSON)
Buildings Explorer
Creating Custom Labels [Soon]
Account & Preferences
Account & Preferences
Creating a User Account
Deactivating a User Account
Admin Vs User Permissions [Soon]
Setting Unit Preferences [Soon]
Security
Security
Security Brief

Troubleshooting Installation & Working with IT

If this is your first time installing Onboard's Edge Software, this guide is for you. Network environments and IT policies can sometimes introduce challenges. This guide outlines the most common troubleshooting steps and how to work effectively with your IT team to get things up and running.

If you have successfully installed the Edge Software and powered on the VM, but the deployment status in the Onboard App remains Offline, work through the checks below.

Verify Firewall & Network Permissions

Ensure outbound traffic is permitted from the Edge VM

  • TCP 443 : Required for secure HTTPS communication with Onboard's cloud.

💡 When running in Bridged mode, the Edge VM should appear on the building network as a distinct device with its own IP address. If your IT team enforces outbound whitelisting, provide them the Edge VM's IP address to confirm traffic is permitted to Onboard's servers.

Confirm the VM's Network Adapter Mode

  1. Open your virtualization manager (e.g., VMware).
  2. Locate the Onboard VM and open its Network Adapter Settings.
  3. If the adapter is set to NAT mode, switch it to Bridged mode.
    • NAT mode isolates the VM behind the host machine, preventing it from appearing as a distinct device on the LAN.
    • Bridged mode allows the VM to obtain an IP address on the same subnet as your building's BACnet or Modbus devices which is required for device discovery and data collection.
  4. Restart the VM to apply the change.

Confirm Whitelisting with IT

If your IT department enforces strict firewall rules or MAC-based network access controls:

  • Retrieve the VM's MAC address from your virtualization manager.
  • Share it with your IT team to whitelist the Edge VM for network access.
  • If DHCP is in use, confirm the Edge VM is receiving a valid IP address on the correct subnet.

⚠️ Still Not Connecting?

If all checks are complete and the deployment remains offline:

🤝 Working With IT

A few best practices for a smooth collaboration with your IT or OT team:

  • Share requirements early. Provide your IT team the Network & Connectivity Requirements ahead of time so they can prepare firewall rules and network access before installation day.
  • Reassure them on security. Onboard does not require any inbound firewall access. All communication is outbound. SSH access to the Edge Software is only available through an encrypted WireGuard® VPN tunnel, and only when explicitly enabled during Collector setup.