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.
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.
192.168.86.193)admin)7627 (the HP OXPd web-services port).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/DeviceInfoServiceFor 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.":
To create the certificate exception:
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.
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.
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:
HPHP LaserJet MFP M430With the device showing in Managed Devices, this is the simplest and most reliable install path. Try it first.
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 the Install App process reports an error (TLS failure, timeout, authentication error), confirm that:
If it still fails, fall through to Method 2.
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:
The full Device App Manager UI will now appear. Complete the form:
| Field | Value |
|---|---|
| Device Brand | Select HP from the dropdown. |
| Device IP | The IP address of the HP MFD (e.g. 192.168.86.193) — the same address you accepted the certificate for in Step 1. |
| Device Serial | The HP device serial number (e.g. THBTT5R1HC). Found on the device label or under Information → Device Information in the EWS. |
| Admin Username | The HP device administrator username — typically admin. |
| Admin Password | The HP device administrator password. |
When all fields are completed, click Install App. The extension will push the Umango button onto the device.
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.
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).
192.168.86.193).| Field | Value |
|---|---|
| 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 / Password | Leave blank unless your deployment requires HTTP basic auth. |
| Initial Request Query String | user=$AUTHUSER_USERNAME$&redirect=true |
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.
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.
| Symptom | Likely 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. |