alexa_media_player: 500 Internal Server Error

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.

Describe the bug

When I try to log in to Amazon.de via Alexa Media Player integration. It gives me then the Captcha and then I always end up with a “500 Internal Server Error / Server got itself in trouble”. This also happens when I replace the Local URL with the Public (Nabu Casa) URL.

To Reproduce

Setup the Integration and Login to your Amazon Account

Expected behavior

My expected behavior was that I would then see my Alexa devices in the Home Assistant.

Screenshots

image

System details

  • Home Assistant Core Version: 2024.10.4
  • Home Assistant Supervisor Version: 2024.10.3
  • Home Assistant Operating System Version: 13.2
  • Home Assistant Frontend Version: 20241002.4
  • alexa_media version (from const.py): 4.13.7
  • alexapy version (from pip show alexapy in homeasssistant container or HA startup log):
  • Is Amazon 2FA/2SV enabled <!—We will not debug login issues if unanswered—> (y/n): n
  • Amazon Domain: amazon.de

Debug Logs (alexa_media & alexapy) Please provide logs.

Additional context

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Reactions: 4
  • Comments: 49

Most upvoted comments

I never see a captcha logging in to Amazon except for this plugin

tldr: If you have an AWS account using the same email as your Amazon.com account, recreate your 2SV within Amazon.com and try again.

Just adding to the possible problems: I used to have an old Amazon 2SV created years ago within AWS that applied to my Amazon account as well. Never had a problem with this using Amazon products, but today I tried to install this integration and got stuck with the 500 error message.

I was about to change my 2SV method on Amazon.com to phone and noticed it was listed as “None”, which was weird. I recreated the MFA, and it worked on the first attempt 🎉 I even noticed that my old MFA code had more than double the size than the current one, so it might be something related to AWS/Amazon account changes that happened a few years ago.

@johnpc Did you get it to work?

I tried the login with several devices (android smartphone, notebook, pc) and I always got the captcha. Even when I try different browsers. So I dont think its a cache / browser setting problem.

I’ve also noticed that the URL contains an error after sending the captcha:

http://10.1.1.4/auth/alexamedia/proxy/errors/validateCaptcha?amzn=vNeUyZ2LWkUl0BXuKFI

And I’ve noticed that the website which shows the captcha and the login form is always based on amazon.com, even if I set amazon.de in HASS.

I believe it has nothing to do with the HA host but rather the settings in your browser you are accessing HA from or possibly Amazon account settings…

I ran into that as my password was wrong - maybe double check it.

Same. Tried multiple iterations of URLs and such. Still the same issue.