Hello everyone,
First of all I have already searched the forums and checked Digi’s tutorials.
As the title says I would like to establish a connection between the gateway (ConnectPort X2) and Digi Device Cloud.
I have followed the tutorials and trouble shouters but haven’t managed to do it yet.
I have set my DNS to use Google’s (8.8.8.8 ; 8.8.4.4), set the cloud address “developer.idigi.com”, etc. but it cannot connect.
I tried pinging the cloud’s IP via the “Diagnostics” in “System Information” and it returns this error : “error: ping failed, error 118: Destination unreachable: no route”.
Any help would be much appreciated!
Regards,
Benjamin
That domain name has been decommissioned. I recommend trying the latest: my.devicecloud.com.
Thank you for the advice. I tried with the URL you gave but there is still the same issue.
If I cannot connect to the device cloud I’d like to know at least how to save the data collected from a python script on a file in the gateway.
Thank you for the advice. I tried with the URL you gave but there is still the same issue.
If I cannot connect to the device cloud I’d like to know at least how to save the data collected from a python script on a file in the gateway.
Are you able to ping the device cloud domain from the command line of the Digi unit?
If not, is there a DNS configured on the unit under the Network > Advanced Network Settings menu from the web interface?
Otherwise, you could try the IP address instead: 52.73.23.137 (although this is subject to change).
As for Python, you might want to make a separate posting under the Python category.
Thank you for your comment.
No I am not. As said in the description my DNS is configured to use Google’s and I get this error : “error: ping failed, error 118: Destination unreachable: no route” when I try to ping any IP address.
Here is my Event Logging :
+0 days 00:00:00 boot Unit started.
+0 days 00:00:00 yaffs System indicates YAFFS.
+0 days 00:00:00 time Applying system time adjustment threshold of 60 seconds.
+0 days 00:00:00 time Lost time source recovery is enabled.
+0 days 00:00:00 system Product: ConnectPort X2D (ID 0x00B2).
+0 days 00:00:00 system Firmware Version: 2.17.1.0 (Version 82002549_F1 11/05/2013).
+0 days 00:00:00 system Boot Version: 1.1.3 (release_82002547_A).
+0 days 00:00:00 system Post Version: 1.1.3 (release_82002548_B).
+0 days 00:00:00 system Product VPD Version: release_82002550_A.
+0 days 00:00:00 system Hardware Strapping: 0x0775.
+0 days 00:00:00 yaffs checkBootParm: YAFFS 010000a0 (eth0)
+0 days 00:00:00 dcloud Device ID: 00000000-00000000-00409DFF-FF88F640
+0 days 00:00:00 dcloud Vendor ID: 0xFE000000
+0 days 00:00:00 dcloud Device Type: ConnectPort X2D
+0 days 00:00:01 mesh Radio version: HW 0x1d47 FW 0x1061
+0 days 00:00:02 dcloud Starting device-initiated connection.
+0 days 00:00:02 dcloud Finding Service, URL=en://my.devicecloud.com
+0 days 00:00:02 dcloud Trying TCP.
+0 days 00:00:02 dcloud DNS resolution failed for my.devicecloud.com.
+0 days 00:00:02 dcloud TCP failed.
+0 days 00:00:02 dcloud Connection to server failed, server=my.devicecloud.com
+0 days 00:00:02 dcloud Device-initiated connection failed, return=-2
+0 days 00:00:02 dcloud Service Down - Can’t Connect.
+0 days 00:00:02 dcloud Will reconnect to server in 60 seconds.
Make sure you have a static DNS server configured under the Network > Advanced Network Settings on the ConnectPort X2D unit.
You mention you have google DNS configured. Are you able to ping that IP address from the ConnectPort X2D command line?
Is the priority set to Static?
Reading this further, based on your inability to ping anything, it appears you may have something more going on than simply DNS configuration. Do you have a gateway configured that will route to the internet?
It is also possible your company (or WAN provider) is blocking unknown protocols on port 3198.
I think that’s the port the device to cloud socket uses - I haven’t looked for a long time. I believe there is a knowledge base article warning of what ports need to be open.
If cellular is involved (I know you imply not because of ‘X2’), I have seen folks like verizon ‘punish’ devices which try to bypass there own DNS. So the query still worked, but could take more than a minute for the response to return. So use their DNS, and it is fast & peppy - use 8.8.8.8 and your DNS results will be bad.