1 Answer
- Newest
- Most votes
- Most comments
3
Hi. It's AWS_IO_SOCKET_CONNECTION_REFUSED: https://github.com/awslabs/aws-c-io/blob/9678fcec01c21bb98e86c957367448d4e3695880/include/aws/io/io.h#L115. AWS_ERROR_ENUM_BEGIN_RANGE(AWS_C_IO_PACKAGE_ID) evaluates to 1024.
Relevant content
- asked 3 months ago
- Accepted Answerasked 4 months ago
- Accepted Answerasked 2 months ago
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 months ago
- AWS OFFICIALUpdated 2 months ago
Hi Greg, thanks for your answer, seems that Im having the same problem. Couldnt find alternatives about root cause, can you give us some clues?
thanks
Hi Greg, we are still trying to fix this error without success. Do you have any clue about why this is happening? Or how to solve it?
The tunnel is already created and the devices connected but we cant ssh to the remote device because of this.
Thanks in advance.
Regards,
Hi. The secure tunneling component is a special build of AWS IoT Device Client, and this error message comes from here: https://github.com/awslabs/aws-iot-device-client/blob/cf738c82927f5a0020a58fda88a5de65b11a4574/source/tunneling/TcpForward.cpp#L107. Does your device meet all the requirements (specifically is the secure tunneling endpoint reachable and is port 443 open)? https://docs.aws.amazon.com/greengrass/v2/developerguide/secure-tunneling-component.html#secure-tunneling-component-requirements
Thank you Greg for your helpful comment on this post. @JoseMi what Greg has mentioned is right. You have to name sure the port is accessible otherwise component will not be able to establish a connection.