http://192.168.1.55:8123/auth/alexamedia/proxy/verify 500 Internal Server Error Server got itself in trouble #2133
Replies: 9 comments 1 reply
-
Same her any solutions will be helpfull |
Beta Was this translation helpful? Give feedback.
-
I have the same issue, no matter what I do. Credentials and 2FA are all confirmed. |
Beta Was this translation helpful? Give feedback.
-
Same problem also. Y try with several fixed by google without success |
Beta Was this translation helpful? Give feedback.
-
I noticed in the debug logs of HA that the calls were being rejected because of authentication issues. I don't know how to resolve that though. |
Beta Was this translation helpful? Give feedback.
-
Same problem after new pw set |
Beta Was this translation helpful? Give feedback.
-
I ran into this problem today after updating to the latest alexa media player from HACS and a reboot. I was originally specifying a public facing DNS and when I switched to specifying the local dns address with valid SSL certificate (https) and it worked. I see that OP was using http, maybe there's a hard requirement for this to be https with valid certificate? |
Beta Was this translation helpful? Give feedback.
-
Mine is totally broken as well after updating my Amazon password. Errors out, cannot enable skill. |
Beta Was this translation helpful? Give feedback.
-
same as Armand29 I Changed password internal error 500 instead of list of devices |
Beta Was this translation helpful? Give feedback.
-
Hi everyone. I've the same problem. I deleted the integration after 2024.8 problem. I can't reconfigure the integration. |
Beta Was this translation helpful? Give feedback.
-
I updated my Amazon password in Italy
I went to update the credentials on the app where I confirmed the password and solved the anti-robot question
it gives me error 500
How do I solve it?
http://192.168.1.55:8123/auth/alexamedia/proxy/verify
Error
500 Internal Server Error Server got itself in trouble
Beta Was this translation helpful? Give feedback.
All reactions