jonpetersathan

@wickedathletes Open any movie from your library in plex and look at the URL

Glad to hear it worked! I should probably add it to the guide as well then.

@Goldoni Can you check, if you have Webhooks enabled? Plex Server Settings / Network / Webhooks (Advanced View) If yes and it is still not working, maybe try enabled Push Notifications as well: Plex Server Settings / General / Push Notifications (Advanced View) Restart Plex afterwards. If that also doesn't work, hit me up with a PM and we will figure this one out

@Goldoni Can you reach (ping) your PA container from within your Plex container? If not, what network adapter are you using? Bridge or Host? It doesn't matter if you are using binhex or the official Plex container. If you have the correct IP in your Plex Webhook URL and both containers are able to communicate, you should at least see "Inbound request" if you start playback of any movie.

Should be fixed now, update your container to the latest version. Is there anything displayed in your logs, if you add a new movie? Be aware that it takes a couple of seconds before plex sends a library.new event to the webhook. If plex does so, you should see something like "Inbound requests... Handling new movie announcement..." in your logs.

Yes, open PA's log from the Unraid GUI and start playback of any plex movie. If the log is displaying something like "Inbound request... Ignoring event not of type library.new" then everything is working correctly.

Hey all, I've updated the container and guide above to work with environment variables now, so if you have any trouble try the following: 1. Stop and Remove the PlexAnnouncer container. 2. Delete the template file. (Run from terminal: rm /boot/config/plugins/dockerMan/templates-user/my-PlexAnnouncer.xml) 3. Install PlexAnnouncer and set it up accordingly. 4. Double check your are running the latest image, by clicking Docker / Check for Updates within Unraid.

If you changed the port in both the Plex Webhook URL and PA Settings, it should work. Note, that the port displayed as "Listen on ..." within the containers logs will always be 32500, since it refers to the local port of the container. The Docker daemon will "reroute" the port to whatever you specified in the settings tab. Nvm, just noticed Unraid is passing through the external port as environment variable, so I changed the log output, just update the container.

Yeah, I didn't get env vars working at the first try and I prefer having all my config in appears to back them up easily, but since you all seem to have trouble with the config file, I should probably reconsider this. Shouldn't be to hard to implement. Thanks for the feedback anyway, really appreciate it! I will take a look at this over the weekend and give you guys an update.

@roadkill Plex sends constantly updates via the webhook, for example if you play/pause a movie. Make sure you add a new movie to plex. It must not be scanned by plex before, so removing one and adding it again does not work. If the movie appears in plex under "Recently Added" then plex will send a "library.new" event to PlexAnnouncer which then sends a Discord message (this may take a couple of seconds). Also note that currently only movies are supported (not tv shows or music tracks).

@Goldoni: Your config looks alright so far. The problem seems that the container is not able to find the config file. Make sure to change the "Config Path" to something like "/mnt/user/appdata/plex_announcer/" and then, after creating the container edit the file generated e.g. with "nano /mnt/user/appdata/plex_announcer/config.json"

Yes, it is supposed to stay running, after you modified the config file accordingly. The first time you run it, it will create a basic config file and then error out since of the missing discord webhook credentials. Is there anything being displayed in the logs? (Right click container / Logs) Also make sure that your DISCORD_WEBHOOK_ID looks like 819835938443493436 and your DISCORD_WEBHOOK_TOKEN should look like pMCEZmx8HG9qeLzpDukzHOCnbLjtXf4YSCpIMGaEt4M2YOu7LrcdMhNnFF9CWsaXF7kf.

Summary: Support Thread for Tenasi - PlexAnnouncer DockerHub: https://hub.docker.com/r/tenasi/plexannouncer Project: https://github.com/tenasi/plexannouncer Note: A Plex Pass is required to configure webhooks! What is PlexAnnouncer? PlexAnnouncer is a Discord bot that sends updates about newly added Plex media to a Discord channel of your choice using webhooks. Basically it proxies plex webhooks to discord. The bot itself is written in Python 3 and is using discord.py and aiohttp. Getting Started / Configuration 1. Create a Discord webhook and copy the webhook url. Goto Server Settings / Integration / Webhooks / Add Webhook. Setup a profile picture (e.g. this) and name and copy the Discord Webhook URL. 2. Install PlexAnnouncer from the Unraid CA store. Make sure that PlexAnnouncer is in the same Network as your Plex container. Paste the Discord Webhook URL and enter some random token for your Plex Webhook (can be any alphanumeric value). Last but not least you have to tell PlexAnnouncer your Plex server URL (so it can link to it). Your server URL should look like this: https://app.plex.tv/desktop#!/server/SERVERID You can copy it from your browsers address bar, if you click on any movie within your library. 3. Add a new webhook in Plex. Goto Plex / Settings / Webhooks / Add Webhook and enter the following url: http://IP:PORT/PLEX_WEBHOOK_TOKEN Replace IP with the address of your container or localhost in case you are running Plex and PlexAnnouncer on the same host. Replace PORT with your external port you mapped (default: 32500) and finally append your Plex Webhook token you specified earlier. Also make sure you have both Webhooks and Push Notifications enabled: Plex Server Settings / Network / Webhooks (Advanced View) Plex Server Settings / General / Push Notifications (Advanced View) 4. Whitelist libraries (Optional) If you wish to get updates only of specific libraries, add a new environment variable called UPDATED_LIBRARIES and specify the libraries (comma separated) you want to receive updates from. Note: If you configured PA based on the old guide, the config file is now deprecated, but still functional. However if you encounter any issues, try using env vars instead. About Us GitHub Profile: https://github.com/tenasi DockerHub Profile: https://hub.docker.com/u/tenasi If you like our work, please consider supporting it: https://paypal.me/tenasi