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!…Continue reading How to get your Azure IoT Edge runtime to use port 443 instead of using 5671 and 8883?

Everything is broken (a delicious lego meme)

“Unable to retrieve IoT Edge informationIoT Edge configuration uses an unsupported schema and cannot be displayed.” after deploying from VS Code. What do?

This article explains a couple of steps you might need to take when executing a Single-Device deployment from Visual Studio Code to an Azure IoT Edge device. Through a bit of trial and error, I learned quite a few things that might go wrong when VSCode is building your deployment…Continue reading “Unable to retrieve IoT Edge informationIoT Edge configuration uses an unsupported schema and cannot be displayed.” after deploying from VS Code. What do?

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!