rrubin0
commented
7 months ago TL;DR - Alexa hates your proxy, use https.
I'm running Home Assistant Core on Docker, and I've been using Alexa Media Player for a few years now, ever since the early betas and it has proven to be solid. I recently renamed one of my dot devices, which naturally caused it to become unavailable within Home Assistant. In my attempts to add the device back, I deleted the integration to simply add it again, with a fresh list of included devices. This turned into a bit of a nightmare, as I experienced the dreaded "500 Internal Server Error" described here.
I tried numerous ways to resolve the connection. Again, it was working fine, I just wanted to add the renamed device back, so I already had 2FA established and a successful connection from Amazon to HA. I finally determined that the problem must be due my migration to NGINX using http instead of the native https connection I used to have when I originally set up Alexa MP. I tried to add a proxy rule to allow the Amazon sign in, and I also tried to add the 2FA key manually. Neither method worked.
What solved the issue for me permanently On a hunch, I decided that I would try going back to https to see if Alexa MP could successfully connect. This worked EFFORTLESSLY using the preferred authentication method in the integration (no long key needed). It authenticated on the sign in page without hesitation, accepting the 2FA code and instantly added the integration back to my HA with my newly renamed device back online and happy. After testing successfully, I changed my firewall rules back as they were, using NGINX and http and the integration still works fine.
To temporarily enable https, I created a new subdomain with my DNS provider, then I configured LetsEncrypt certbot to issue a new certificate using the new subdomain and modified my firewall policies to: temporarily disable my inbound https:443 -->HA directly and created a rule to forward/translate inbound https:443 -->HA:8123.
Then I edited configuration.yaml to include:
## enable ssl to use hassio url:8123 ##
http:
ssl_certificate: !secret ssl_cert
ssl_key: !secret ssl_keyThen I restarted HA, which was now accessible at: https://newsubdomain.myhaserver.com:8123 I used this new address when setting up the integration so it could perform the authentication, and it continues to work after moving it all back to http and letting NGINX handle SSL as it did before.
I'm not an NGINX expert, so I'd be curious if someone smarter knows of a proxy rule that does work. For me, this was not trivial, but it was a heck of a lot faster than the other methods that I tried or were suggested in this thread and ultimately more secure too.
jazzmonger
dakidjersey
alandtse
pbolo
BatemanJo9
stas1000
MaJerle
harobertocpf
github-actions[bot]
p0onage
ps915
phieb
gianniocchipinti
IMPORTANT: Please search the issues, including closed issues, and the FAQ before opening a new issue. The template is mandatory; failure to use it will result in issue closure.
see also #2136
Describe the bug
I am new to HA and want to install Alexa Media Player. All went fine until I have to do the captcha. There I am running into a 500 error. Even if I want to get a new picture. The path I have mydomain.org:8123/auth/alexamedia/proxy/verify
To Reproduce
fresh install restart Home assistant add integration alexa media player fill the configuration (amazon unser, amazon, password, amazon.de for region, home assistant url, 2FA key) and send check the OTA key
login for alexa is comming up prefilled amazon login and password press button to login
captcha is showing (/auth/alexamedia/proxy/ap/signin/144-3911749-1675617) clicking on "neue Zeichen anzeigen" causes an 500 (Server got itself in trouble) or filling the captcha question is doing the same
Expected behavior
The integration shall install proper
Screenshots
System details
const.pyor HA startup): 4.80pip show alexapyor HA startup): 2023.12.0Logs Please provide logs.
Additional context