How to get your Azure IoT Edge runtime to use port 443 instead of using 5671 and 8883?

Are you struggling with your Azure IoT Edge modules not receiving your Direct Method calls? Is EdgeHub reporting transient network issues? Are you seeing “Could not connect to your IoT hub: could not complete TLS handshake” errors? Are your modules experiencing constant 104 errors (connection reset by peer)? Fear not! This article explains how to fix them. Kind of. Problem We were experiencing some major issues with our customer’s Edge devices. Direct Method calls would mostly not go through, message routing between Edge and the…Continue reading How to get your Azure IoT Edge runtime to use port 443 instead of using 5671 and 8883?

Azure IoT Edge is just Docker containers all the way

Azure IoT Edge gotchas – and how to overcome them!

This article describes the gotchas and weird one-offs that I’ve encountered with Azure IoT Edge so far. Consider them not-too-thoroughly tested quick fixes that aren’t significant enough to warrant an actual blog post themselves :) Okay – let’s get to them gotchas, then! Posts Related to “Azure IoT Edge gotchas – and how to overcome them!”:How to update application settings of an Azure Functions App in Azure DevOps PipelineHow to authenticate against npm registries in Azure DevOps?How to access invisible packages in Azure DevOps artifact…Continue reading Azure IoT Edge gotchas – and how to overcome them!

Azure IoT Edge is just Docker containers all the way

How to fix “Cannot start service edgeHubDev: Ports are not available: listen tcp 0.0.0.0:8883”

Here is another fun one for the books! In this article, I will explain how to fix a problem with the Azure IoT Edge dev simulator, when it fails to start due to an underlying problem with Docker not having access to your defined ports. This will probably happen to one of the ports used by the Edge Hub system module by default – 5671, 8883, or 443. Problem So, when you’re trying to run an Azure IoT Edge solution in the simulator, you get…Continue reading How to fix “Cannot start service edgeHubDev: Ports are not available: listen tcp 0.0.0.0:8883”

Docker - sure, it works great!

How to fix “exec user process caused: no such file or directory” in Docker on Windows?

Another one in the series of “random things that break when you try to run Docker on Windows”! I was just minding my own business, trying to run an Azure IoT Edge custom module – a Docker container, really – locally, when suddenly everything broke and one of my Docker containers wouldn’t run anymore, which broke the rest of my stuff pretty badly. Instead, it failed with a cryptic and surprising error “exec user process caused: no such file or directory”. So, let’s take a…Continue reading How to fix “exec user process caused: no such file or directory” in Docker on Windows?