Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Sickbeard/Couchpotato plex notifications

Featured Replies

So, i got the docker images setup but ran into a problem with Sickbeard/Couch notifications to plex.

 

When creating the container using -h hostname as specified in the getting started guide it assigns a Ip address on the internal docker range.

 

When either program connects to plex since we are on another ip range compared to plex it causes Authentication to be required. However both of these programs provide no support to provide the authentication information for the PMS.

 

Currently i solved this by using the --net="host" it works fine since the unraid box Ip is on the same Ip range as plex.

 

Running with --net is not recommended according to the docker documentation since it allows access to DBUS on the host.

 

Wondering if anyone has figured out a  way to get notification to work without using --net.

 

you can add the docker network to the "list of networks that are allowed without auth" in plex.

goto the server settings -> network -> advanced.

 

type

172.17.0.0/255.255.0.0

in the text field.

(note, this was posted somewhere before, couldn't find the post)

  • Author

That worked.

 

Hopefully this will help someone out if they stumble upon it.

 

Thanks for the help.

Fixes my SB/CP Plex notifications but breaks my local network discovery  :(

  • 2 weeks later...

You probably need to add your local sub-net too..

 

172.17.0.0/255.255.0.0, 192.168.1.0/255.255.255.0

 

or whichever you use..

  • 9 months later...

I'm running in to this same issue with the latest plex, sickbeard, and sabnzbd dockers.  Basically, I can't seem to get Plex and Sickbeard to talk so that Plex receives the notification.  I did put 172.17.0.0/255.255.0.0 in to the list of trusted networks in Plex, but it didn't work.  Has anyone else resolved this issue recently?

The issue is related to the Plex Home changes that were implemented several months ago.  There are no unauthorized connections allowed to your plex server anymore.  Sickbeard has not been patched to support this.  If you like sickbeard, i believe sickrage (a fork of sickbeard) contains this functionality. The other alternative is Sonarr, which is what i moved to and enjoy.

The issue is related to the Plex Home changes that were implemented several months ago.  There are no unauthorized connections allowed to your plex server anymore.  Sickbeard has not been patched to support this.  If you like sickbeard, i believe sickrage (a fork of sickbeard) contains this functionality. The other alternative is Sonarr, which is what i moved to and enjoy.

 

Several months ago?  Are we sure about this?  I was using Sickbeard with notifications to Plex just fine a couple weeks ago.  Of course that was not using unRAID 6.0 and Dockers so I guess those notifications were "authorized" (plugin with unRAID 5.0) whereas when Sickbeard with a Docker under unRAID 6.0 is "unauthorized?" 

After re-reading the Plex Home documentation . If you don't have a Plex Home setup (multiple users) this doesn't appear to apply.  I don't have a way to test this, so i can't be 100% sure. In the sickbeard config are you referencing plex via the IP address of your unraid server?

After re-reading the Plex Home documentation . If you don't have a Plex Home setup (multiple users) this doesn't appear to apply.  I don't have a way to test this, so i can't be 100% sure. In the sickbeard config are you referencing plex via the IP address of your unraid server?

 

Yes.  It is the server's ip:32400.  This was pretty much the same way I had it setup before on unRAID 5.0, but I think the Dockers add an additional hurdle and it feels like something does need to be put in to Plex under the "list of networks that are allowed without auth" (go to the server settings -> network -> advanced).

 

I'm just not sure exactly what that should be. 

 

Just in case this might help someone else who ran in to this same issue, I'm not so sure that a PLEX notification is even needed for Plex anymore.  I've been watching the behavior of my server without PLEX notifications and PLEX seems to almost instantaneously pick up when there has been a change made to the media and is singularly scanning that specific folder.  These two switches can be turned on in the settings of PLEX. 

 

I haven't spent much time testing, but for now I'll leave this as-is and not worry about the notifications.  Hopefully, it will continue to operate as it is now over the long-term.

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.