Plex - 429 Too Many Requests

Today I started getting error "429 Too Many Requests" on all of my Plex Channels I added to Channels DVR. The stream plays for about 45 seconds to a minute and then terminates.

Here is what is in the log file from stream start to when it cuts off:
2023/02/21 20:46:32.175538 [HLS] Starting live stream for channel 9707 from (bitrate=4362)
2023/02/21 20:46:35.083866 [HLS] ffmpeg: ch9707-dANY-ip192.168.2.3-remux: [hls @ 00000000012bd940] Timestamps are unset in a packet for stream 1. This is deprecated and will stop working in the future. Fix your code to set the timestamps properly
2023/02/21 20:46:35.260216 [HLS] Probed live stream in 3.0846786s: h264 1920x1080 progressive 4233760bps
2023/02/21 20:47:25.730386 [TNR] Closed connection to M3U-PlexTV for ch9707 Ax Men Presented By History
2023/02/21 20:47:25.730386 [SNR] Buffer statistics for ch9707 Ax Men Presented By History: buf=0% drop=0%
2023/02/21 20:47:26.524943 [HLS] Couldn't generate stream playlist for ch9707-dANY-ip192.168.2.3: Stream stopped
2023/02/21 20:47:26.524943 [HLS] Stopping transcoder session ch9707-dANY-ip192.168.2.3 (out: 54.041333s, finished: true)
2023/02/21 20:47:27.710894 [ERR] Failed to start stream for ch9707: M3U: Could not fetch playlist: get 429 Too Many Requests

Any suggestions?

I'm getting the same thing too. I had several recordings this evening from a PLEX channel that all had this and got all interrupted.

@gladnerjr what version of the server are you running? I'm at version 2023.02.20.2151.

Yeah.. It didn't do this earlier today.. It started sometime in the afternoon from what I can tell.

@mjitkop I am currently running version 2023.01.23.1746 on both of my servers.

OK so the server version doesn't make a difference in this case.

Since this is a custom channel source, I'm not sure the developers can do much about it, even if it says "Fix your code to set the timestamps properly" in the logs.

By the way, I see this is your first time here. Welcome! :slight_smile:

1 Like

Thanks! Appreciate the warm welcome.. I did reach out to @matthuisman (the FrndlyTV for Channels GOD and keeper of the .m3u8 files I am using) in a message to give him a heads up.. Not sure this issue is in his wheelhouse but he did respond.

So at least I know I am not crazy and I am the only one this is happening to! Thanks very much for responding to let me know.

1 Like

I've been recording the TV show "Wahlburgers" on the channel "Perform Presented by Lifetime" (for me, it is channel #11653). There was a mini marathon tonight and there are still a few more episodes to be recorded and will fail.

I will submit diagnostics in case the developers will be willing to take a look.
I'm not sure who would need to "Fix [their] code to set the timestamps properly". :grin:

Logs have been submitted as 21a714fe-69fb-490a-9636-db399dc51665 .

even their API on website gives same error half the time while navigating epg.
They have some stupid small restrictions on their api.
lets give it a few days and see if improves

1 Like

I got this then it went away for a few days and now it looks like it is back. Anyone get any more information?

Having this issue now.

Also having this issue. Would love to know if anyone has a solution.