alexa_media_player: BUG: error indicates auth process using IP not host name to do SSL verfiication
Describe the bug & steps to repro
I setup integration via hacs.
Added integration in integrations panel
in the config i added my amazon username, password and external accessible hostname for home assistant (e.g. https://myname.mydomain.com (this uses a wildcard cert issues by comodo and that is trusted by amazon)
was proxied redirected to amazon
authenticated with amazon
was redirected back to https://[myextenraldnsname]/auth/alexamedia/proxy/ap/signin
then got this:
https://<internalip>/auth/foomedia/proxy/ap/signin/<redacted>; please retry: Cannot connect to host <internalip>:443 ssl:True [SSLCertVerificationError: (1, "[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: IP address mismatch, certificate is not valid for '<internalip>'. (_ssl.c:1125)")]
it needs to be using a host name, not the IP address… or the SSL verification will never work.
System details
- Home-assistant (version):
core-2021.3.2
supervisor-2021.03.4
- Hassio (Yes): (Please note you may have to restart hassio 2-3 times to load the latest version of alexapy after an update. This looks like a HA bug).
- alexa_media
v3.8.2
- alexapy
1.24.2
- Amazon [2FA is disabled] (using new proxy method)
Logs Please provide logs. We’ll be most likely asking for them anyway.
Additional context Add any other context about the problem here.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 17 (7 by maintainers)
Commits related to this issue
- Merge pull request #1219 from alandtse/#1203 fix: fix case where proxy receives ip address only — committed to alandtse/alexa_media_player by alandtse 3 years ago
No. But I’ll leave this open until I propagate the fix.