Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

[paulrjbagnall]

Describe the bug

Home assistant did an update. Rebooted. AMP didn't load. Attempted to remove link to account and re-add. Didn't work. Uninstalled AMP, reinstalled. Now when go to add integration, get the following error:

Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

To Reproduce

I would simply say update Home Assistant...

Expected behavior

It to just work, add devices and link properly. Won't even simply add the integration at this point. Fully removed plugin from HACS and reinstalled too.

Screenshots

System details

• Home Assistant version: 2025.7.3
• alexa_media version (from const.py or HA startup log): v5.7.5
• Is Amazon 2SV via Authenticator App (not 2SV OTP via SMS) enabled? <!---We will not debug login issues if unanswered---> (y/n): y
• Amazon Domain: .co.uk

[nebakanezzer]

same happening with amazon.com

[paulrjbagnall]

Looks like it's an issue with the latest Home Assistant Core version (if you're on 2025.7.2 like i was, as it happened the minute i ran the update) -- it also looks like an issue directly related to something called 'alexapy' -- seems to correct when you downgrade....

Run command: ha core update --version 2025.7.1

Worked for me and hope it helps you :)

[nebakanezzer]

Installation method
Home Assistant OS
Core
2025.7.3
Supervisor
2025.07.1
Operating System
16.0
Frontend
20250702.3

took a snapshot of the VM, will try that and see

edit

did not work. same error.

[robert-kau]

I am with the same error with amazon.com.br

Installation method
Home Assistant OS
Core
2025.7.3
Supervisor
2025.07.1
Operating System
16.0
Frontend
20250702.3

[nebakanezzer]

just figured this out. for some reason, it accepts your password in the pop up web window, but it will not tell you it is wrong. I changed my password to my amazon account, redid setup, and it worked. I don't think my password was actually wrong either, I think just resetting it triggers something that allows it to continue. it is possible it has old pw stored for instance, and thinks they are correct, but cannot validate them (because they are wrong). in any event, change your password and try setting up the integration agian

[alandrdre]

I am also having this issue and finding it impossible to setup I end up on this web page after entering my login details twice. http://192.168.0.36:8123/auth/alexamedia/proxy/verify
But I get:
500 Internal Server Error
Server got itself in trouble

I tried doing this from my local ip in an ingognito browser to eliminate some of the variable such as nginx, etc that could get in the way.
I've tried with 2fa on and off with entering the 2fa authentication into the config flow
I've tried changing the password.
I've tried direct setup in config.yaml

This integration has worked for me in the past.
I'm on HA 2025.7.4 and using V2.0.5 (i tried rolling this back as well)
Can't get this back since I uninstalled and tried to reinstall due to echo devices unavailable.
I can't work out anything else to try. Anyone else having issue? Any ideas what I can try?
I tried rolling back HA
Apologies if I'm not posing this in the right place or format. It seemed like this thread was roughly along the same lines as what I'm getting.
But I'm pretty stuck with this. Can anyone help?

[iorifly]

Same with me

[chebanco]

Hi, I have same trouble with amazon.fr -> error 500 :[

Is there any solution or a way to get more details of the error?

[iorifly]

my problem was that the password was wrong.

[chebanco]

@iorifly Thank you so much I was sure of pwd and it was not the good one.
This is solved