This article will discuss how to configure your Digi TransPort router for use with Remote Manager by utilizing the built-in Web User Interface (WebUI) of the Digi TransPort itself.
The Digi TransPort WebUI can be accessed locally via the local IP address (LAN or WAN), or the Cellular Mobile IP address (provided your cellular account is one which supports Mobile Termination, and that you left a pinhole for HTTP or HTTPS through which to get to the WebUI if configured for IP Passthrough).
If you know the
Mobile IP address and have met the conditions above, you should be able to open the TransPort's WebUI by opening a browser to the Mobile IP of your TransPort at this time, but keep in mind that accessing the TransPort WebUI via the
Local IP is preferred if available, since it doesn't affect your cellular bill, is faster, and generally less prone to connection loss.
If you can get to the
Local IP of the TransPort (this is an Ethernet or Wi-Fi connected TransPort and you're at that location), you should access the TransPort's WebUI using the
Local IP address instead. The
Digi Device Discovery Tool for Windows can be used to discover the
Local IP address of the TransPort, if unknown (and assuming that the "ADDP" Service is running on the TransPort). If you run the Device Discovery Tool and see a "No devices found?" message, and you've verified your TransPort is both powered on and has a solid Link LED present, you may want to check this article for
Digi Device Discovery Troubleshooting Tips.
Assuming you can access either the Mobile (WAN) or Local (LAN) IP address and are now looking at the Web UI of your Digi TransPort:
1. Open
Configuration - Remote Management > Remote Manager
NOTE: Prior to 5.2.13.4 firmware, there was a drop down menu in which you could select either remotemanager.digi.com or remotemanager-uk.digi.com. After 5.2.13.4, changing the Remote Manager server is done via the TransPort CLI (Command Line Interface) via the "cloud 0 server" command (see step 4 below).
2. On the page above, ensure the "
Automatically reconnect to the server after being disconnected" box is checked and configured with the 10 second value listed (or a reasonable alternative), as this is the box that tells your router to re-connect to the Remote Management server, should the connection get broken for some reason.
3. Apply any changes by clicking the
Apply button, when configuration is complete.
4. Go to
Administration - Execute a command and enter the following command to see what server is currently being used as the Remote Manager server:
cloud 0 server ?
Digi currently recommends that "my.devicecloud.com" be used for the Remote Manager server. If your server is different, it may be changed via the following command:
cloud 0 server my.devicecloud.com
Then save the configuration and reboot the TransPort:
saveall
reboot
5. After a minute or so, you should see that your TransPort has established (i.e. state = ESTAB) a Remote Management connection to the Remote Manager server by viewing the
Management - Connections > IP Connections page under the “
General Purpose Sockets” listing towards the bottom:
In Closure: If all went well, your Digi TransPort should now be “Connected” on the Digi Remote Manager server.
The screenshot just below shows the Device Cloud tile, which is located at the top-right of the default TransPort web interface landing page (after logging in).
You are now ready to add your Digi TransPort to the Remote Manager server:
HOW TO: Add a Digi TransPort to your Remote Manager account, if you haven't done so already.
If you have any problems after completing this guidance, you may need to
contact Digi Technical Support for further assistance.