Issues with Plex ping and integration
Hi, i'm having a couple issues with my plex configurations on homarr: ping isn't working due to return status 401 and neither the widget is.
I'm running Homarr 0.15.3 on Portainer and I've followed Plex's documentation in order to retrieve the correct token.
11 Replies
Thank you for submitting a support request.
Depending on the volume of requests, our team should get in contact with you shortly.
⚠️ Please include the following details in your post or we may reject your request without further comment: - Log (See https://homarr.dev/docs/community/faq#how-do-i-open-the-console--log) - Operating system (Unraid, TrueNAS, Ubuntu, ...) - Exact Homarr version (eg. 0.15.0, not latest) - Configuration (eg. docker-compose, screenshot or similar. Use ``your-text`` to format) - Other relevant information (eg. your devices, your browser, ...)
❓ Frequently Asked Questions | Homarr documentation
Can I install Homarr on a Raspberry Pi?
Hi, status 401 is normal. pings being a general function, they don't use the integration tokens resulting in "401 unauthorized". if the plex server was down you wouldn't have that code so it's safe to just add that code under the "network" tab of the app.
Regarding the widget, could you please share more information? such as the logs as refered by Cakey bot
this is the only log i can find reguarding plex:
failed to communicate with media server 'Plex' (517efda7-8d6f-4ac3-8995-0b9a83a44a25): TypeError: fetch failed
You need to get the console/container log, see the link given by cakey bot
i guess this would be the only error
not in your browser, in your container's console
the previous log ( ERROR failed to communicate with media server 'Plex' (517efda7-8d6f-4ac3-8995-0b9a83a44a25): TypeError: fetch failed) is the only log i could find in the container console
Ah sorry, I thought it was a browser error. Why sharing only parts of the logs? There might be something in the rest of it.
Unfortunately this error is very vague, I'll try checking around
Ah, maybe I see the problem
Solution
use http instead of https
You're right, it was a stupid mistake on my side...
Thanks a lot for your help and the prompt response!
No problem. the 401 itself would have happened anyway so this is understandable. Have a good one