-
Notifications
You must be signed in to change notification settings - Fork 291
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cant authenticate anymore #2379
Comments
I have the same problem: since I updated to the beta version, it hasn't been working and it doesn't allow me to log in. |
I have the same problem: since I updated to the beta version. 2024.8.0b |
are you sure, that it is the same issue and not this: #2378 (with 2024.8.0b0) |
Same here, after update to 2024.8.0b0 |
Also having same issues as mentioned |
'Unknown error occurred'. The logs say:
|
Same of the above confirmed. This is my first time to integrate this and face now this issue. Oh lord thank you. Amazon may have changed something on its end again. |
Same issue here since update to 2024.8.0b0 |
I am still on 2024.7.4 |
Same here, I was hoping to come on here and find a solution :-( |
This is the wrong issue to post that to. This one is for initial configuration & can't authenticate. Yours is post initial config i.e. reconfigure. Your issue might be strings translation for your language is missing? or your browser has cached incorrect files from before when strings translation wasn't updated yet. Try clearing your browser cache! To actually answer your question though, this is the reconfigure Options screen after you've successfully installed & configured the integration and then you select the configured integration's CONFIGURE options. The fields are:
|
Update for those having problems: |
@Flexigem Also in Home Assistant 2024.08 Beta? Or 2024.07? |
@Matze89x - probably not on the 2024.8 beta - as the issue is within the upstream library alexapy. the other issues caused alexamediaplayer not working on 2024.7. are related to a fix, trying to solve some deprication messages. |
So what exact version of what do we need to get that running again? |
if you are on 2024.7 use the 4.12.1 of alexa media player for now. |
This is the way |
any way to revert manually, if you dont have a backup? My n |
Not working for me. I am on 2024.7 and 4.12.1 . Trying a new Install throw an Error 500 on /auth/alexamedia/proxy/verify |
hm... that's probably not an issue of the integration itself. Can you post the complete error log? |
Here it is :
|
ok, it seems, that the integration is running into a timeout waiting for a response.
|
Ok, but what can I do then ? It's throwing the 500 error after like 3 seconds. |
Ah wait. This is a complete different topic... And probably just a similarity that it happened around the same time. I am sorry, but I can't further Support in thus topic as I am Not yet deep enough in the Integrations programming... :-( |
Describe the bug
When authenticating, it returns to my HA with this url (censored): https://xxxxxxxx8c0y15d6n4k62yqay.ui.nabu.casa/auth/alexamedia/proxy/verify and then returns this:
500 Internal Server Error
Server got itself in trouble
This happened after i updated to the 2024.8b version. I reverted to 2024.7.4, but still have the same problem, so not sure if its related.
The text was updated successfully, but these errors were encountered: