Installing the Umango Cloud Embedded App on HP MFDs

Installing the Umango Cloud Embedded App on HP MFDs

Overview

This article walks you through installing the Umango embedded app onto an HP Multi-Function Device (MFD). HP devices expose their OXPd web services over HTTPS using a self-signed certificate, which most browsers (and operating systems) reject by default. This creates a hurdle that may require some manual intervention. Before any install tool can talk to the device, you must first teach your browser to trust that certificate.

The recommended browser for the certificate-exception flow is Mozilla Firefox, which provides a straightforward, per-site exception process.

Three installation methods — try them in order

Once the Firefox certificate exception is in place, attempt the install methods below in order. The first method works for the large majority of devices; the others are fallbacks for the small number of cases where the first one fails.

Install from the Umango Managed Devices screen
Tick the device in Umango and click Install App. Works for the vast majority of HP MFDs.

Method 2 — Fallback

Install from the Umango browser extension popup
Use the hidden Device App Manager in the extension popup (five-click unlock).

Method 3 — Last Resort

Install with the HP OXPd Button Manager utility
A standalone HP utility (available from Umango Support) for advanced or stubborn cases.

Before you begin

What you will need

  • Firefox browser — required for the certificate-exception workaround.
  • Umango account access — you must be logged in to Umango in Firefox.
  • HP device details:
    • Device IP address (e.g. 192.168.86.193)
    • Device serial number (printed on the device or visible in the EWS)
    • HP device admin username (typically admin)
    • HP device admin password
  • Network access — your workstation must be able to reach the device on TCP port 7627 (the HP OXPd web-services port).
  • (For Methods 1 or 2) The Umango browser extension installed and pinned to the Firefox toolbar.
  • (For Method 3 only) The HP OXPd Button Manager utility — available from Umango Support.

Step 1 — Create a certificate exception in Firefox

This step is required for installation methods 1 or 2 and must be repeated for each HP device you intend to install onto.

Open Firefox and navigate to the HP device's OXPd DeviceInfoService URL, replacing {DeviceIp} with your device's IP address:

https://{DeviceIp}:7627/hp/device/webservices/OXPd/DeviceInfoService

For example, for a device at 192.168.86.193:

https://192.168.86.193:7627/hp/device/webservices/OXPd/DeviceInfoService

Firefox will display the security warning "Be careful. Something doesn't look right.":

Firefox security warning showing 'Be careful. Something doesn't look right' for the HP device URL
Figure 1 — Firefox security warning for the HP device's self-signed certificate.

To create the certificate exception:

  1. Click Advanced.
  2. Click Accept the Risk and Continue (or Proceed to {IpAddress} (Risky), depending on Firefox version).

Firefox will now permanently remember the exception for this device. You should see a small XML/SOAP response page — that's normal and confirms the device is reachable.

Why this is required

HP MFDs ship with a self-signed TLS certificate that no certificate authority has signed. Without an exception, Firefox (and the install tools that rely on it) will refuse to connect to the device, and the install will silently fail or time out.


Step 2 — Create the device entry in Umango

To use the preferred install method (Method 1), the device must first exist in the Umango Managed Devices list. In most cases this happens automatically if the device is on the same network as a running Umango instance, it will be auto-discovered within a few minutes.

If the device does not appear automatically, add it manually:

  1. In Umango, navigate to Devices and click Force Discovery.
  2. In the Device Discovery dialog, switch to the Manual Entry tab.
  3. Complete the device information:
    • Device BrandHP
    • IP Address — the device's IP
    • Serial Number — the HP serial number
    • Device Model Name — e.g. HP LaserJet MFP M430
  4. Click Submit.
Umango Device Discovery dialog on the Manual Entry tab with Device Brand HP, IP address, serial number and device model name fields filled in
Figure 2 — Adding the device manually via Force Discovery → Manual Entry.

With the device showing in Managed Devices, this is the simplest and most reliable install path. Try it first.

  1. Navigate to the Managed Devices screen in Umango.
  2. Locate the row for the HP device you want to install onto.
  3. Tick the checkbox at the left of that row to select the device.
  4. Click the Install App button in the toolbar above the list.
  5. If the admin credentials are not the factory default, enter the password using the Device Password button.
Umango Managed Devices screen with the HP LaserJet MFP M430 row checked and the Install App button highlighted in the toolbar
Figure 3 — Select the device in the Managed Devices list, then click Install App.
Verify the install

Walk to the device's front panel (or refresh the device's home screen via the EWS) and confirm that the Umango button now appears alongside Copy, Scan and Fax.

If this method fails

If the Install App process reports an error (TLS failure, timeout, authentication error), confirm that:

  • The Firefox certificate exception from Step 1 was created in the same Firefox profile you're currently using.
  • The IP address and serial number on the device row match the physical device.
  • The admin credentials you provided are correct.
  • You have refreshed the Umango page after the Browser Extension was installed

If it still fails, fall through to Method 2.


Method 2 — Install from the browser extension popup

If Method 1 fails, the Umango browser extension contains a hidden Device App Manager that performs the install with slightly different plumbing. With the Firefox certificate exception still in place and Umango logged in:

  1. Click the Umango browser extension icon in the Firefox toolbar to open the popup.
  2. In the popup, click the Umango logo (the small colored circle) five times in quick succession. This unlocks the Device App Manager.
Umango extension popup with an arrow indicating to click the Umango logo five times
Figure 4 — Click the Umango icon in the extension popup five times to reveal the Device App Manager.

The full Device App Manager UI will now appear. Complete the form:

Umango Device App Manager showing Device Brand HP, Device IP, Device Serial, Admin Username and Password fields with Install App button highlighted
Figure 5 — The Umango Device App Manager. Select HP, enter the device details, then click Install App.
FieldValue
Device BrandSelect HP from the dropdown.
Device IPThe IP address of the HP MFD (e.g. 192.168.86.193) — the same address you accepted the certificate for in Step 1.
Device SerialThe HP device serial number (e.g. THBTT5R1HC). Found on the device label or under Information → Device Information in the EWS.
Admin UsernameThe HP device administrator username — typically admin.
Admin PasswordThe HP device administrator password.

When all fields are completed, click Install App. The extension will push the Umango button onto the device.

Why five clicks?

The Device App Manager is an advanced tool intended for administrators and support technicians. Hiding it behind five successive clicks prevents accidental access by end users who do not need these features of the extension.

If this method also fails, proceed to Method 3.


Method 3 — Install via HP OXPd Button Manager (last resort)

If both Umango install paths fail, you can install using the standalone HP OXPd Button Manager utility, available from Umango Support. This tool talks to the device's OXPd interface directly and gives you finer control over the installed button (custom icon, alternative URI, region-specific Umango cloud).

HP OXPd Button Manager utility showing connection fields, existing buttons list with Umango selected, and the button details edit pane
Figure 6 — The OXPd Button Manager utility. Fill in the connection and button details, then click Add/Update Button.

Step-by-step

  1. Launch OXPd Button Manager.
  2. In the Connect to the Device section, enter:
    • Hostname or IP — the device's IP address (e.g. 192.168.86.193).
    • Admin Password — the HP device administrator password.
  3. Click Retrieve Button Data to populate the existing buttons list. Any previously installed Umango button will appear here.
  4. In the Edit Button Details section, enter the following:
    FieldValue
    Button ID (UUID)Click Generate a New UUID for a new install, or keep the existing UUID when updating.
    Button Title (en-US)Umango
    Button Description (en-US)Umango connected to server https://{your-tenant}.{region}.umango.cloud
    Button URI (Web App URL)https://{your-tenant}.{region}.umango.cloud/mfd/init/hp/{DeviceSerial}
    HTTP User Name / PasswordLeave blank unless your deployment requires HTTP basic auth.
    Initial Request Query Stringuser=$AUTHUSER_USERNAME$&redirect=true
  5. (Optional) Click Browse next to the icon preview to upload the Umango SVG icon supplied by Umango Support. SVG is preferred for crisp scaling on all panel sizes; PNG/BMP/JPG are also accepted via Advanced.
  6. Click Add/Update Button to push the button to the device.
Region matters

Make sure the Button URI points to the correct regional Umango cloud data location (e.g. demo.us.umango.cloud, demo.de.umango.cloud, demo.au.umango.cloud) and your unique tenant name. Using the wrong region will result in the button opening to an authentication failure.


After installation — assigning jobs

Once the Umango button is installed on the device, you can assign workflows / jobs to it from Umango as normal. If the device wasn't already in Managed Devices when you installed (for example you used Method 2 or Method 3 against a device Umango didn't yet know about), follow the Step 2 instructions to add it manually so it can be managed.


Troubleshooting

SymptomLikely cause & resolution
Install App from Managed Devices fails with TLS / connection error The certificate exception in Step 1 has not been created in the same Firefox profile, or the device IP has changed. Re-run Step 1 with the exact IP shown on the device row.
"Authentication failed" or 401 returned from the device Admin username/password incorrect, or the device's admin account is locked. Log in to the device's Embedded Web Server (EWS) to verify the credentials.
Device does not auto-discover Firewall or VLAN may be blocking discovery traffic. Use Force Discovery → Manual Entry (see Step 2) to add the device manually while the network path is investigated.
Five clicks on the extension icon does nothing Clicks may be too slow — they need to be in quick succession (within ~3 seconds). Close the popup and try again. Confirm you are logged in to Umango in the same browser.
Umango button appears on the device but launches an error page The Button URI is pointing to the wrong Umango cloud region, or the device serial in the URI is incorrect. If you used that method 2 to install the app, make sure you had Umango dashboard open and in the current tab while deploying the app to the device. Double-checking and re-install.
Port 7627 times out HP OXPd web services may be disabled on the device. In the device EWS, navigate to Networking → Web Services (path varies by model) and enable OXPd.
All three methods fail Capture screenshots of each failure and contact Umango Support with the device model, firmware version, IP, and serial number.


    • Related Articles

    • Installing Umango Silently Using Command Line Properties

      This article explains how to install Umango without user interaction by running the installer from the command line and supplying MSI properties. The Umango installer is distributed as an EXE bootstrapper that contains an MSI package. For silent ...
    • Umango Scan Actuator Troubleshooting

      This article walks you through diagnosing connection problems between the Umango Scan Actuator (the small desktop app that talks to your scanner) and the Umango web application running in your browser. If you're on a personal or home computer, start ...
    • Changing SNMP Settings in Umango

      Umango uses SNMP (Simple Network Management Protocol) to discover and interact with supported multifunction devices (MFDs) on the network. These settings can be customized via the Advanced Configuration Screen. Default SNMP Settings By default, ...
    • Umango Installation Issue - SQL Server 2017 Compatibility

      Overview Umango installations include Microsoft SQL Server 2017 Express as a prerequisite for database functionality. In some environments, the installation of SQL Server 2017 Express may fail, preventing Umango from installing successfully. This ...
    • Restricting User Access to Umango in Azure

      By default, when you create an Azure App Registration for use with Umango authentication, any user within your Microsoft Entra ID (formerly Azure AD) tenant can authenticate. To restrict access to specific departments, teams, or individuals, you must ...