Issue with Simultaneous Operation of Plex Ping Check and Media Server Widget

ajnart / homarr

Customizable browser's home page to interact with your homeserver's Docker containers (e.g. Sonarr/Radarr)

https://homarr.dev

MIT License

5.48k stars 253 forks source link

Issue with Simultaneous Operation of Plex Ping Check and Media Server Widget #2013

Closed schoppfe closed 2 months ago

schoppfe commented 2 months ago

Environment

NodeJS

Version

0.15.2

Describe the problem

Hi,

I am experiencing a problem in Homarr where the Plex Ping Check and the Media Server Widget cannot operate at the same time. Configuring the internal URL as http://plex.local:32400 enables the Ping Check to function correctly, but the Media Server Widget fails to connect. Conversely, when I append /web to the URL, the Media Server Widget connects, but the Ping Check stops working. Could someone please check if this behavior is consistent?

Thank you.

Logs

No response

Context

No response

Please tick the boxes

[X] I confirm that I attached the proper logs
[X] I've read the docs
[X] I've checked for duplicate issues
[X] I've tried to debug myself

github-actions[bot] commented 2 months ago

Hi 👋. Thank you for submitting your first issue to Homarr. Please ensure that you've provided all nessesary information. You can use the three dots > Edit button to update your post with additional images and information. Depending on the current volume of requests, the team should get in conact with you shortly.

schoppfe commented 2 months ago

I was able to resolve the issue by configuring the '401 Unauthorized' error as an indication of being online. Is this a safe solution? Perhaps this could be added to the documentation to assist others who might encounter the same confusion.

schoppfe commented 2 months ago

miss-clicked

SeDemal commented 2 months ago

It is safe, that's what we do recommend. Searching our discord or this GH's closed issues most likely will show you others going through the same thing. We could add it to our documentation, but in reality, there are edge cases were this is an erroneous solution (such as behind certain reverse proxies). I guess this is why we haven't added it. Same goes for the error code 403 that some user end up getting for PiHole.