Iot Edge device module connection refused "HTTPConnectionPool , Errno 111 Connection refused "

Amit V 21 Reputation points
2021-06-25T12:50:17.797+00:00

109338-screen-shot-2021-06-25-at-51038-pm.png

No response from classification service
HTTPConnectionPool(host='testclassifier', port=80): Max retries exceeded with url: /image (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7f7a7588d0>: Failed to establish a new connection: [Errno 111] Connection refused'))

Connectivity checks

-------------------

√ host can connect to and perform TLS handshake with IoT Hub AMQP port
√ host can connect to and perform TLS handshake with IoT Hub HTTPS port
√ host can connect to and perform TLS handshake with IoT Hub MQTT port
√ container on the default network can connect to IoT Hub AMQP port
√ container on the default network can connect to IoT Hub HTTPS port
√ container on the default network can connect to IoT Hub MQTT port
√ container on the IoT Edge module network can connect to IoT Hub AMQP port
√ container on the IoT Edge module network can connect to IoT Hub HTTPS port
√ container on the IoT Edge module network can connect to IoT Hub MQTT port
√ Edge Hub can bind to ports on host

No errors are showing up when I do iotedge check

109376-screen-shot-2021-06-25-at-51700-pm.png

The ports which are listening on the IoT edge jetson nano

How do I resolve this error?

Azure IoT Edge
Azure IoT Edge
An Azure service that is used to deploy cloud workloads to run on internet of things (IoT) edge devices via standard containers.
534 questions
Azure IoT Hub
Azure IoT Hub
An Azure service that enables bidirectional communication between internet of things (IoT) devices and applications.
1,115 questions
0 comments No comments
{count} votes

1 answer

Sort by: Most helpful
  1. Sander van de Velde 28,311 Reputation points MVP
    2021-06-25T22:02:38.68+00:00

    Hello @Amit V ,

    which module do you want to deploy? Is this module publicly available? Is there a GitHub repo to examine?

    From the logging, it seems a classification service is called at HTTP address "/image".

    This looks like a relative path, therefore it cannot be reached, causing the error message.

    It probably should have been an absolute path. Perhaps you are missing some configuration?

    1 person found this answer helpful.