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 Server got itself in trouble #12

Open
4 tasks done
helmarw opened this issue Jul 9, 2024 · 1 comment
Open
4 tasks done

500 Internal Server Error Server got itself in trouble #12

helmarw opened this issue Jul 9, 2024 · 1 comment

Comments

@helmarw
Copy link

helmarw commented Jul 9, 2024

System Health details

Homeassistant Docker on Synology NAS DS1821+
Core 2024.1.2
Frontend 20240104.0

Checklist

  • I have enabled debug logging for my installation.
  • I have filled out the issue template to the best of my ability.
  • This issue only contains 1 issue (if you have multiple issues, open one issue for each issue).
  • This issue is not a duplicate issue of currently previous issues..

Describe the issue

after trying to add this integration, thats all im getting: 500 Internal Server Error Server got itself in trouble

no idea where to start. log-file not really helpful. im looking at the files listed but no clue why there si a problem
and idea ?

Reproduction steps

follow installation instructions
it shows up when searching for MediaBrowser but cannot add Integration

Debug logs

2024-07-09 11:43:12.118 WARNING (SyncWorker_1) [homeassistant.loader] We found a custom integration mediabrowser which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
  File "/config/custom_components/mediabrowser/config_flow.py", line 90, in async_step_user
  File "/config/custom_components/mediabrowser/discovery.py", line 22, in discover_mb
  File "/config/custom_components/mediabrowser/discovery.py", line 31, in _discover_message
  File "/config/custom_components/mediabrowser/config_flow.py", line 90, in async_step_user
  File "/config/custom_components/mediabrowser/discovery.py", line 22, in discover_mb
  File "/config/custom_components/mediabrowser/discovery.py", line 31, in _discover_message

Diagnostics dump

No response

@ghost-03
Copy link

I don't think this project is maintained, but I had a similar problem, also with Docker on a Synology NAS. What helped is that I modified the 'discovery.py' file in the plugin, and changed the hostname in line 32 from socket.gethostname() to "localhost". After a restart, the plugin worked as expected. Possibly either the NAS or the Docker confused Python. Hope this helps.

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

2 participants