Skip to content
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

500 Internal Server Error on SetUp #2704

Open
RowMax03 opened this issue Nov 29, 2024 · 14 comments
Open

500 Internal Server Error on SetUp #2704

RowMax03 opened this issue Nov 29, 2024 · 14 comments

Comments

@RowMax03
Copy link

RowMax03 commented Nov 29, 2024

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

So i tried setting up the integration for ca 40mins now. Dosen't matter if I choose amazon.de or .com use Otp or not after the Alexa sign in screen pops up. It either says that my account dosen't exist or it will give me Captcha challange which will result in a 500 Server Error.

To Reproduce

  1. Go to 'Install'
  2. Click on 'Submit'
    Try to Sign in into Amazon Alex Account
  3. See error

Expected behavior

Sign in/Account Linking working

System details

  • Home Assistant version:
    Core
    2024.11.3
    Frontend
    20241106.2
  • alexa_media version (from const.py or HA startup log):
    5.0.0
  • 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): y, tried first without and then with on .com and .de
  • Amazon Domain: .com/.de

Debug Logs (alexa_media & alexap
home-assistant_2024-11-29T01-52-26.043Z.log
y)

Please provide [logs]Additional context

It could be the case that the Amazon Servers are currently not working correctly because its 2:30 in the night

@MaJerle
Copy link

MaJerle commented Nov 29, 2024

Same issues here.

@samsonusmc
Copy link

Same and following

@Kospolo
Copy link

Kospolo commented Nov 30, 2024

Same here. Following.

@Reecem98
Copy link

Same issue. Following

@malosaaa
Copy link

After setting up same error as you guys here the log

Logger: homeassistant.util.package
Source: util/package.py:152
First occurred: 5:35:22 AM (3 occurrences)
Last logged: 5:35:27 AM

Unable to install package alexapy==1.29.4: × No solution found when resolving dependencies: ╰─▶ Because alexapy==1.29.4 depends on aiofiles>=23.1.0,<24.0.0 and aiofiles>=24.1.0, we can conclude that alexapy==1.29.4 cannot be used. And because you require alexapy==1.29.4, we can conclude that your requirements are unsatisfiable.

@hendmele
Copy link

same here

@Fullmojjo
Copy link

Same here

@danielbrunt57
Copy link
Collaborator

After setting up same error as you guys here the log

Logger: homeassistant.util.package
Source: util/package.py:152
First occurred: 5:35:22 AM (3 occurrences)
Last logged: 5:35:27 AM

Unable to install package alexapy==1.29.4: × No solution found when resolving dependencies: ╰─▶ Because alexapy==1.29.4 depends on aiofiles>=23.1.0,<24.0.0 and aiofiles>=24.1.0, we can conclude that alexapy==1.29.4 cannot be used. And because you require alexapy==1.29.4, we can conclude that your requirements are unsatisfiable.

alexapy 1.29.4 does not support HA Core 2024.12 yet.
Core 2024.12 updated Python from 3.12 to 3.13 and aiofiles from 23.1.2 to 24.1.0
Currently, alexapy requires aiofiles 23.x...

@MaJerle
Copy link

MaJerle commented Nov 30, 2024

@danielbrunt57 The OP has version 2024.11.

Home Assistant version:
Core
2024.11.3

@danielbrunt57
Copy link
Collaborator

@danielbrunt57 The OP has version 2024.11.

Home Assistant version:
Core
2024.11.3

I realize that but I was not replying to the op but @malosaaa, who should not have posted his error here as his error is due to HA Core 2024.12.0b# where python is now 3.13 and aiofiles is 24.1.0.

@randywgreen
Copy link

User error for me... I was using the wrong email/password combination on the configuration UI causing it to result in a 500 error as to be expected.

@danielbrunt57
Copy link
Collaborator

User error for me... I was using the wrong email/password combination on the configuration UI causing it to result in a 500 error as to be expected.

Otherwise known in IT support as a PEBKAC issue - Problem Exists Between Keyboard And Chair! 😊

@thefunkygibbon
Copy link

sigh, literally every single time i got to install this bloody plugin it seems to be broken in some way.

@RowMax03
Copy link
Author

RowMax03 commented Dec 2, 2024

Tp be fair the issue is likely on Amazon. During Setup Amazon was telling me that the account I am using isn't signed up (It is, I used it in the Alexa app to doublecheck and the signup process it was defaulting to was telling me that the email was already used). Sadly however it's on the devs of this plugin to fix it or give clearer instructions for eu users maybe?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests