Firmware Updates Through a DRM Proxy

This article explains the limitation of firmware updates when a DRM proxy is configured and describes the available methods for updating device and modem firmware in proxy-restricted environments.

This is a known limitation.

Locally initiated device firmware updates and OTA modem firmware updates are performed over HTTPS (TCP port 443) directly to the firmware.devicecloud.com server. These updates do not use the EDP connection and therefore cannot use the configured DRM proxy.

Device Firmware Updates via a Proxy

If device firmware updates must be performed through a proxy, initiate the firmware update from Digi Remote Manager (DRM) instead of using the local Web UI or Admin CLI.

When the update is initiated from DRM:

DRM transfers the firmware update to the device through the proxied EDP connection.

The device receives the firmware package through the existing DRM communication channel.

The update can be completed without requiring direct access to firmware.devicecloud.com.

Modem Firmware Updates

For modem firmware updates, the available options are:

Allow direct access to the firmware server

Configure the firewall to allow the DAL device to access firmware.devicecloud.com over TCP port 443.

The device can then download the modem firmware directly from the firmware server.

Perform a local modem firmware update

Download the required modem firmware file.

Upload and install the firmware locally using the device's Web UI.

Important Notes

Device firmware updates initiated locally do not use the DRM proxy.

OTA modem firmware updates do not use the DRM proxy.

Only device firmware updates initiated from DRM can be delivered through the proxied EDP connection.

Modem firmware updates currently require either direct HTTPS access to firmware.devicecloud.com or a manual local update process.

 

Last updated: Aug 21, 2026

Recently Viewed

No recently viewed articles

Did you find this article helpful?