Azure-Samples / Azure-Samples/iotedge_config_cli

After running the script, sometimes we get the error in iotedge check, sometimes not

Open
#22 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
8
Forks
15
PR merge metrics
No merged PRs in 30d

Description

Getting this from lower layer:

```
Connectivity checks
-------------------
√ container on the default network can connect to upstream AMQP port - OK
× container on the default network can connect to upstream HTTPS / WebSockets port - Error
Container on the default network could not connect to 10.126.18.54:443
√ container on the default network can connect to upstream MQTT port - OK
√ container on the IoT Edge module network can connect to upstream AMQP port - OK
× container on the IoT Edge module network can connect to upstream HTTPS / WebSockets port - Error
Container on the azure-iot-edge network could not connect to 10.126.18.54:443
√ container on the IoT Edge module network can connect to upstream MQTT port - OK
```

However, the system works just fine and the certificate looks fine.

![977cad28-f653-4d9e-9768-6ea64c08b3e5](https://user-images.githubusercontent.com/2320572/180572559-dc6ee01b-cab0-447a-b7d8-41b0c1ae449a.jpg)

![a6ea3f71-2321-421f-8c1c-6632b4c798e2](https://user-images.githubusercontent.com/2320572/180572565-06a1d229-cbe2-4a97-bb63-cfbcc86f5157.jpg)

It was fixed after doing `sudo iotedge config apply` again. Which is weird the last command in the `install.sh` is also `config apply`. Why do you need to do it twice in a row?

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.