Closed derSchtefan closed 1 year ago
@derSchtefan thanks for reporting this issue. Are you able to run your scenario using a VM or physical device? Does it only fail in the simulator?
@marianan everything works perfectly fine on VMs and physical devices. it only fails in the simulator.
Got it, thanks for confirming. The issue is in our backlog. We will share updates here when available.
You can work around this by passing the command-line argument BypassCertVerification=true
to the OPCPublisher module. See: https://docs.microsoft.com/en-us/azure/industrial-iot/reference-command-line-arguments
@derSchtefan I could run the OPCPublisher and debug in a custom filter module in local edgeHub dev with the proposed setting from mawax.
"settings": {
"image": "mcr.microsoft.com/iotedge/opc-publisher:2.8.3",
"createOptions": {
"Hostname": "opcpublisher",
"Cmd": [
"--BypassCertVerification=true",
"--an=IIoTAdapter",
Does it work for you as well?
This issue can be closed. Since the version 2.9.0 Preview 4 this issue is fixed.
Thank you for the notification. Closing.
When I run an IoT edge solution containing OPCPublisher from Microsoft, the module keeps restarting with the errors below. It seems something goes wrong during communication with the edge agent / edge hub, something with the TLS certificate is wrong?