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
Plex Sensor stays unavailable after server restart, is behind reverse proxy #67402
Comments
plex documentation |
Hey there @jjlawren, mind taking a look at this issue as it has been labeled with an integration ( |
Non-stale |
This is the fallback portion of the Are you saying that even after the Plex server is running again and Traefik is properly serving in front that the HA Plex integration still will not connect? If it hits this error it should retry until it's able to successfully connect again. |
I agree with your suggested approach, thanks for taking a look. Sorry it took a while for such a simple fix, hopefully this will prevent your issue from recurring. |
Thank you for the fix! :) |
The problem
I have Plex "hidden" behind Traefik. When the Plex server is down, the URL could return
502 bad gateway
or404 not found
errors (I have HA and Plex set up in different locations, so I can't use a direct connection).Today Plex was restarted (during the regular container upgrades), and the Plex integration in HA says
Failed to set up
ever since. The last error in the logs is the following:From what I can see — the reason is in this code:
core/homeassistant/components/plex/__init__.py
Lines 148 to 157 in c95a72d
but I'm not sure what would be the best solution here.
What version of Home Assistant Core has the issue?
2022.2.9
What was the last working version of Home Assistant Core?
No response
What type of installation are you running?
Home Assistant Container
Integration causing the issue
plex
Link to integration documentation on our website
https://www.home-assistant.io/integrations/plex/
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
No response
The text was updated successfully, but these errors were encountered: