Mstrlink1 Posted November 20, 2022 Share Posted November 20, 2022 Hello. I'm having issues getting PA to work. I've been troubleshooting awhile but still no luck. Any suggestions? At thisi point I'm able to get Inbound Requests for Play and Stop events but nothing else. I've tested adding movies and shows. I've checked my Plex settings and confirmed webhook settings look good. I've restarted both Plex+PA and here are my latest logs... 2022-11-20 12:16:16 INFO Plex webhook URL: http://localhost:32500/123347789112325789961121135458947 2022-11-20 12:17:33 INFO 192.168.1.163 [20/Nov/2022:20:17:33 +0000] "GET /123347789112325789961121135458947 HTTP/1.1" 405 210 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36" 2022-11-20 12:17:33 INFO 192.168.1.163 [20/Nov/2022:20:17:33 +0000] "GET /favicon.ico HTTP/1.1" 404 179 "http://192.168.1.134:32500/123347789112325789961121135458947" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/107.0.0.0 Safari/537.36" 2022-11-20 12:17:34 INFO Inbound request 2022-11-20 12:17:34 INFO Request rejected. Event type of media.scrobble. 2022-11-20 12:17:34 INFO 192.168.1.134 [20/Nov/2022:20:17:34 +0000] "POST /123347789112325789961121135458947 HTTP/1.1" 200 156 "-" "PlexMediaServer/1.29.1.6316-f4cdfea9c" 2022-11-20 12:17:52 INFO Inbound request 2022-11-20 12:17:52 INFO Request rejected. Event type of media.stop. 2022-11-20 12:17:52 INFO 192.168.1.134 [20/Nov/2022:20:17:52 +0000] "POST /123347789112325789961121135458947 HTTP/1.1" 200 156 "-" "PlexMediaServer/1.29.1.6316-f4cdfea9c" ======== Running on http://0.0.0.0:32500 ======== (Press CTRL+C to quit) 2022-11-20 12:25:43 INFO Inbound request 2022-11-20 12:25:43 INFO Request rejected. Event type of media.play. 2022-11-20 12:25:43 INFO 192.168.1.134 [20/Nov/2022:20:25:43 +0000] "POST /123347789112325789961121135458947 HTTP/1.1" 200 156 "-" "PlexMediaServer/1.29.1.6316-f4cdfea9c" 2022-11-20 12:25:50 INFO Inbound request 2022-11-20 12:25:50 INFO Request rejected. Event type of media.stop. 2022-11-20 12:25:50 INFO 192.168.1.134 [20/Nov/2022:20:25:50 +0000] "POST /123347789112325789961121135458947 HTTP/1.1" 200 156 "-" "PlexMediaServer/1.29.1.6316-f4cdfea9c" 2022-11-20 12:26:03 INFO Inbound request 2022-11-20 12:26:03 INFO Request rejected. Event type of media.play. 2022-11-20 12:26:03 INFO 192.168.1.134 [20/Nov/2022:20:26:03 +0000] "POST /123347789112325789961121135458947 HTTP/1.1" 200 156 "-" "PlexMediaServer/1.29.1.6316-f4cdfea9c" Quote Link to comment
jonpetersathan Posted November 21, 2022 Author Share Posted November 21, 2022 @Mstrlink1 Can you check your Push notification settings? Plex Server Settings / General / Push Notifications (Advanced View) This needs to be enabled in order for "library.new" events to be send to all web hooks. 1 Quote Link to comment
Mstrlink1 Posted November 21, 2022 Share Posted November 21, 2022 23 minutes ago, jonpetersathan said: @Mstrlink1 Can you check your Push notification settings? Plex Server Settings / General / Push Notifications (Advanced View) This needs to be enabled in order for "library.new" events to be send to all web hooks. Thank you! I missed that. Also didn't realize plex has multiple "General" pages. I kept looking in Plex Web-> General. Anyways its working perfectly now. Thank you again 1 Quote Link to comment
ph.neutral Posted October 19, 2023 Share Posted October 19, 2023 2023-10-19 22:26:27 INFO Plex webhook URL: http://localhost:32500/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Traceback (most recent call last): File "/plexannouncer/./main.py", line 110, in <module> web.run_app(app, port=32500) File "/usr/local/lib/python3.10/site-packages/aiohttp/web.py", line 512, in run_app _cancel_tasks({main_task}, loop) File "/usr/local/lib/python3.10/site-packages/aiohttp/web.py", line 444, in _cancel_tasks asyncio.gather(*to_cancel, loop=loop, return_exceptions=True) TypeError: gather() got an unexpected keyword argument 'loop' 2023-10-19 22:26:52 INFO Plex webhook URL: http://localhost:32500/xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx ======== Running on http://0.0.0.0:32500 ======== (Press CTRL+C to quit) hello, what does this mean? Quote Link to comment
jonpetersathan Posted November 19, 2023 Author Share Posted November 19, 2023 @ph.neutral: Do still have this issue? If yes, may I ask what version you are on? Quote Link to comment
animeking1987 Posted January 25 Share Posted January 25 I'm getting this error and I know im putting in the right plex info as i followed the guide to the letter. Quote Link to comment
Xerazal Posted March 20 Share Posted March 20 Is there any way to edit the message of the webhook? I want it to add an @everyone tag at the beginning of the announcement. Quote Link to comment
darkwolf Posted August 15 Share Posted August 15 Has there been a change to Plex, doesn't seem like the docker is able to announce to Plex anymore (last update to my server was 7/21/2024 according to the logs) Quote Link to comment
Hawkins12 Posted August 15 Share Posted August 15 2 minutes ago, darkwolf said: Has there been a change to Plex, doesn't seem like the docker is able to announce to Plex anymore (last update to my server was 7/21/2024 according to the logs) No change that I am aware of. I have all dockers up to date and plex still announces (checked as of today). 1 Quote Link to comment
darkwolf Posted August 15 Share Posted August 15 Thanks for the quick reply! I will debug on my end then. Quote Link to comment
darkwolf Posted August 15 Share Posted August 15 (edited) Dang, still no reason why it is not working I can see. I can ping out inside the container, name resolution works fine, did not make any changes to either plex or discord (that I am aware of) (Though the issues looks like plex, as I WAS getting updates (play stop updates from plex.tv) up until 7/21) I rebuilt the container, so can not access the older run logs. I get the normal 2024-08-14 20:49:25 INFO Plex webhook URL: http://localhost:<yadda/yadda> but nothing after that. Any advice on further troubleshooting? (It had been working great for well over 2 years, THANKS!) Edited August 15 by darkwolf Quote Link to comment
jonpetersathan Posted August 15 Author Share Posted August 15 14 minutes ago, darkwolf said: I rebuilt the container, so can not access the older run logs. I get the normal 2024-08-14 20:49:25 INFO Plex webhook URL: http://localhost:<yadda/yadda> Does this match the URL you have in Plex? In Plex you should have replaced localhost in the URL with the IP or hostname of the Plex Announcer container. Maybe the IP of your container has changed or something. Try doing a curl URL from the Plex container and check if anything pops up in the logs. Quote Link to comment
darkwolf Posted August 16 Share Posted August 16 (edited) 22 hours ago, jonpetersathan said: Does this match the URL you have in Plex? In Plex you should have replaced localhost in the URL with the IP or hostname of the Plex Announcer container. Maybe the IP of your container has changed or something. Try doing a curl URL from the Plex container and check if anything pops up in the logs. Well damn, you know, I didn't even notice what it was showing! HA! Weird thing is... My plex server has been on a different IP for well over a year, but it has been working fine for 2 years... don't know what changed. But this is what my UnRaid config has for fields So, not sure if the fields changed or something else happened. But creating a new instance on Unraid shows the same fields, no place for plex server URL just webhook port Edited August 16 by darkwolf Quote Link to comment
jonpetersathan Posted August 16 Author Share Posted August 16 @darkwolf ah okay, I see what's going on. So first of all, the IP of your Plex server doesn't matter at all. However the IP of PA does. This is because the webhook you configured in Plex directly points to the IP of PA. So if this happens, you need to open webhook configuration in Plex and change and update the URL. (Just copy whatever is in the PA logs at the beginning and replace localhost with the IP of your PA container. This likely happened because you are not using custom networks and restber works and a static IP for your containers. Quote Link to comment
darkwolf Posted August 16 Share Posted August 16 (edited) 15 minutes ago, jonpetersathan said: @darkwolf ah okay, I see what's going on. So first of all, the IP of your Plex server doesn't matter at all. However the IP of PA does. This is because the webhook you configured in Plex directly points to the IP of PA. So if this happens, you need to open webhook configuration in Plex and change and update the URL. (Just copy whatever is in the PA logs at the beginning and replace localhost with the IP of your PA container. This likely happened because you are not using custom networks and restber works and a static IP for your containers. The webhook in Plex is still pointing to the same IP it was before (where PA resides), and the docker is in bridge mode and has been, so is the IP of the server, so not sure what to change, nothing on the network has changed. I could just as easily throw this in a docker on the plex host (I have a few running there already), so I may do that. Edited August 16 by darkwolf Quote Link to comment
darkwolf Posted August 16 Share Posted August 16 (edited) All working now. I forget in my testing last night that I added a digit to my token to force a rebuild of the docker on UnRaid, but did not modify the Plex Webhook URL. Not sure what happened to cause it issues in the first place. But forcing a rebuild seems to have worked! Thank you for being there and the quick replies, as a developer and a Unix Admin for 25 years, it is much appreciated and respected. Edited August 16 by darkwolf 1 Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.