2 Risposte
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
Hello,
That port in the screenshot is not accurate - the actual port in use is 8883. The provider we are using has a translation service for ports and IPs, which is why this looks the way it does.
Thank you, Jonathan
con risposta 3 mesi fa
0
Hi. I think your connection attempt isn't getting far enough to reach AWS IoT Core, hence no logs in CloudWatch. Port 1883 isn't supported: https://docs.aws.amazon.com/iot/latest/developerguide/protocols.html.
Contenuto pertinente
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 2 anni fa
OK. What error does your client report? Are you saying it works most of the time for all your devices, with just occasional connection problems? Do your CloudWatch metrics report any errors or throttles described here: https://docs.aws.amazon.com/iot/latest/developerguide/metrics_dimensions.html#message-broker-metrics
There is no error per se, the connection just gets stuck in limbo (no message is received after the TCP ACK). So the application logic tries to connect again. EDIT: Also, I checked the metrics report and there are no throttles or errors around connect in the last week.