Not able to create container on Azure storage explorer|Azure blob storage on IoT Edge

[raghavrawat98]

I am following this document https://docs.microsoft.com/en-us/azure/iot-edge/how-to-store-data-blob?view=iotedge-2020-11. I have my edge device running at a Linux VM. I deployed the following manifest {

"modulesContent": {
  "$edgeAgent": {
    "properties.desired": {
      "schemaVersion": "1.1",
      "runtime": {
        "type": "docker",
        "settings": {
          "minDockerVersion": "v1.25",
          "loggingOptions": "",
          "registryCredentials": {}
        }
      },
      "systemModules": {
        "edgeAgent": {
          "type": "docker",
          "settings": {
            "image": "mcr.microsoft.com/azureiotedge-agent:1.2",
            "createOptions": {}
          }
        },
        "edgeHub": {
          "type": "docker",
          "status": "running",
          "restartPolicy": "always",
          "settings": {
            "image": "mcr.microsoft.com/azureiotedge-hub:1.2",
            "createOptions": {
              "HostConfig": {
                "PortBindings": {
                  "5671/tcp": [
                    {
                      "HostPort": "5671"
                    }
                  ],
                  "8883/tcp": [
                    {
                      "HostPort": "8883"
                    }
                  ],
                  "443/tcp": [
                    {
                      "HostPort": "443"
                    }
                  ]
                }
              }
            }
          }
        }
      },
      "modules": {
        "raghav": {
          "version": "1.1",
          "type": "docker",
          "status": "running",
          "restartPolicy": "always",
          "settings": {
            "image": "mcr.microsoft.com/azure-blob-storage:latest",
            "createOptions": {
              "Env": [
                "LOCAL_STORAGE_ACCOUNT_NAME=malasrilocalstorage",
                "LOCAL_STORAGE_ACCOUNT_KEY="
              ],
              "HostConfig": {
                "Binds": [
                  "myblobs:/blobroot"
                ],
                "PortBindings": {
                  "11002/tcp": [
                    {
                      "HostPort": "11002"
                    }
                  ]
                }
              }
            }
          }
        }
      }
    }
  },
  "$edgeHub": {
    "properties.desired": {
      "schemaVersion": "1.1",
      "routes": {},
      "storeAndForwardConfiguration": {
        "timeToLiveSecs": 7200
      }
    }
  },
  "raghav": {
    "properties.desired": {
      "deviceToCloudUploadProperties": {
        "uploadOn": true,
        "uploadOrder": "OldestFirst",
        "cloudStorageConnectionString": "DefaultEndpointsProtocol=https;AccountName=malasristorage123;AccountKey=;EndpointSuffix=core.windows.net",
        "storageContainersForUpload": {
          "cont1": {
            "target": "edge-cont1"
          },
          "cont2": {
            "target": "%m-%c"
          },
          "cont3": {}
        },
        "deleteAfterUpload": true
      },
      "deviceAutoDeleteProperties": {
        "deleteOn": true,
        "deleteAfterMinutes": 5,
        "retainWhileUploading": true
      }
    }
  }
}

}

Then in Azure Storage Explorer I was connecting to this storage via connection string:"DefaultEndpointsProtocol=http;BlobEndpoint=http://raghav:11002/malasrilocalstorage;AccountName=malasrilocalstorage;AccountKey=;" I am getting the following error

[MRayermannMSFT]

@raghavrawat98 are you perhaps behind a proxy? If so you can try using system proxy, which you can read about in our networking documentation: https://docs.microsoft.com/en-us/azure/storage/common/storage-explorer-network There are some limitations to it, so make sure you understand those. In the networking docs you can also read about how to configure proxy settings manually if you need to do that instead.

If you are not behind a proxy, then you can confirm if any other programs can reach your IoT storage? The message ENOTFOUND meant that Storage Explorer was not able to reach your IoT storage.

[raghavrawat98]

@MRayermannMSFT I was using an Azure Linux VM for Edge Device and Azure Windows VM for the Storage Explorer. AFter enabling the port,

• sudo ufw enable
• sudo ufw allow 11002
• sudo ufw status numbered I was able to connect.

[JasonYeMSFT]

@raghavrawat98 Are you saying that after allowing the port in our firewall, you are able to create containers on your IoT Edge device?

[raghavrawat98]

@JasonYeMSFT Yes after allowing port in firewall I was able to create containers on IoT Edge device.