Looking for some help with Media Server Widget (Plex integration) and Download Speed widget (nzbget)
Hi! Hope you guys can help me with my new homarr installation, still trying to learn how it all works but run into a few issues, hopefully it's just a problem with me being a bit stupid and doing something wrong.
I will also note I have done some searches online and this discord support channel but I couldn't see anything, if I missed something please let me know.
I have jellyfin and plex both running simultaneously, I've added both to homarr and jellyfin works perfectly with the media server widget, but plex I'm having some issues with.
I have added Plex, without an ending
/ , and input my API key correctly (from the XML on my plex server), and added 401 to my HTTP status codes and it still won't pick it up.
My plex installation is running off the QNAP store, not through docker. The error codes I get are:
Picture:
https://i.imgur.com/Ffnbtlt.png
That's issue one, issue 2 is with nzbget and its integration.
nzbget is working perfectly in the Usenet widget
Picture: https://i.imgur.com/G3IMrwL.png
But the speeds aren't being picked up by the download speed widget, which is confusing me.
I did see these logs:
I'm wondering if my issue is something to do with I do not run nzbget with a password, so I always get stuck on filling out the integration stage with the username and password field, and not being able to progress unless something is in. I've started putting in nzbgets default username and password, and I get my results in the Usenet widget, but the downloader isn't being picked up.
Some information on my system:
I have a qnap system with my docker stack running in a docker swarm config, with a lot of my docker apps in the same compose file (nzbget, radarr, sonarr, homarr etc.), with Plex running as its own standalone app from the qnap store. tautulli can communicate with my Plex server fine, just homarr seems to be having issues. I run my apps through a reverse proxy and oauth service for access.
Anyone got any ideas?
Thanks!Solution:Jump to solution
Nothing's perfect, it may need to be updated again too. Reenter the username and the password
104 Replies
@zwooosh can you send me what your Plex internal address looks like ?
Maybe it’s the issue. Thanks a lot for the detailed description btw
Sure thing! Here's how it looks:
https://i.imgur.com/MMQRFZq.png
And for good measure, here's how nzbget looks:
https://i.imgur.com/5UpMe4H.png
I have solved issue #1, with Plex and the Media Server widget, I just changed the
https:// to http:// and that's solved it. Still working on the nzbget download speed issue#2 are you sure nzbget is a valid url?
The only reason I'd say it is is this screenshot:
https://i.imgur.com/G3IMrwL.png It's picking up the queued list and it can see the progress, size, ETA - even the speed. Just not showing up on the download speed widget
Yeah that's also why I assumed at first that it was but that really doesn't look like it should be valid
This is how my docker apps talk to each other, all apps in the compose file connect to the same internal network so the URLs look like that. For example, this is the structure of my prowlarr config:
https://i.imgur.com/F44mdKB.png
Must be an issue with my setup, since they aren't talking to a recognised URL. I'll open a port on my nzbget and try to get on via my lan.ip.address:port and see if that works
No if that is how it works I do believe it should work. If one widget is working no reason the other shouldn't. Can't you leave the password field empty?
I do think the problem stems from that
No, it doesn't let me weirdly.
Do you think maybe going into the .json and making:
this:
Might help?
Changing the type won't help, it's the value that is used
Sorry that's what I meant, I tried making the username nzbget, with a blank value as password. Now the app flashes between working in the usenet widget, then showing this:
https://i.imgur.com/NfeMz8P.png
Have you tried with just http:// ? For Plex
Oh yeah nice
Try using IP instead of hostname
Aha yeah that was an oversight from my part. All sorted there.
Just tried this, put in the IP and the port and similar issue - I think you guys are right if one widget works perfectly it might be something to do with requiring a username and password from me?