After some days of fighting against this common error (can’t link my skill with Alexa) and follow a couple of times the guide, I’m trying to look for any debugs/logs file that could throw some light into it, because I really don’t know what else to try.
I have HTTPS, duckdns, the NAT is working, I can control HASS from & outside my network, and the test in Lambda works (I can see my devices from there)… the endpoints are ok (EU) too, but still, the iPhone APP refuses to link the skill.
So yep, what I need is the location of the log file that holds the linking error to understand what’s happening down there.
So this is the flow for the linking. The first 2 steps are ok. The problem must come later. Keep digging meanwhile someone points me to the right log location (which seems to be around the authorization server)
Solved! For anyone with strange 443 port behaviors, it could be related to the remote management service that some ISPs use to access the router. In my case (Movistar, Spain), they use 443 to access my router in case something goes wrong. The problem is that this NAT rule goes on top of whatever NAT you configure.
To solve it, disabling MGMT in the router (or changing 443 MGMT to something else) will do the trick. Reboot, and there you will have the 443 correctly following the NAT you have configured.
Argh! 3 days of fighting with the Skill and AWS configuration… anyway. Problem solved.
