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

When launching setup wizard: "500 Internal Server Error Server got itself in trouble" #278

Closed
gerolori opened this issue Jul 13, 2023 · 1 comment

Comments

@gerolori
Copy link

gerolori commented Jul 13, 2023

Unless all relevant information is provided, I can't help you

Describe the bug
I did a clean install of grocy as an addon and tried to delete the non working grocy custom component and start over.
Grocy as addon installed and setted up succesfully (port 9192 visible even outside home assistant, so all good). Custom component deleted, than restarted HA, than installed it again and restart one more time.
When I go in devices and set up the custom component an error pops up after 30 sec or so: Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

Expected behavior
Should prompt the address, api key and port selection window

To Reproduce
Steps to reproduce the behavior:
HA Settings > Devices & Services > Add Integration > Grocy

General information to help debugging:

What sensors do you have enabled? Are they working and/or what state are they in? Do you have the corresponding functions enabled in Grocy?
None, I couldn't set them up

What is your installed versions of Home Assistant, Grocy and this integration?
Home Assistant: 10.3 (Supervisor 2023.07.1)
Grocy: 0.19.1
Grocy custom component: 4.8.0

How do you have Grocy installed? Add-on or external?
Add-on

Have you added debugging to the log, and what does the log say?
Don't know how to do that :(

@gerolori
Copy link
Author

Found out the issue
I'm running home assistant os in a VM, so i tried prerouting port 9192 to the ip of the vm but for some reason it didn't work.
Using the ip of the actual vm and not the one of the host actually worked! Hope it helps someone

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

1 participant