For some reason today none of my media will play. I keep getting the message Couldn’t retrieve the play queue for this item. Please try again. This happens when I try to play a movie and or tv show. Can someone please help me figure out how to fix this. I’m using plex media server 1.28.1.6041-738907df3
Is there anyone there that can help me? Would be nice if someone could actually help instead being captain obvious by closing a duplicate post and not giving any advice for a solution.
1 Like
First rule of Plex is you gotta learn how to help yourself.
And then if you’re going to ask for help, at least provide some info
Have you turned everything off and back on again?
What are you running PMS on?
What are you trying to play back on?
Have you tried playing back on a different player?
Have you tried playing back something you know has worked previously?
Have you gone through the basic troubleshooting steps like optimize database and clean bundles?
When was the last time it worked? What has changed in your setup since then?
Have you searched the error message and tried any of the potential fixes that other people have suggested who have had the same error?
First rule of Plex is, they need to start providing support for their product. We pay, get errors, post the issue, then the discussion is closed with no replies because it is relying on the community.
Have you turned everything off and back on again? Always, there is no need for support if this isn’t tried first.
What are you running PMS on? Synology NAS
What are you trying to play back on? Apple TV Remotely
Have you tried playing back on a different player? Yes, works on my laptop but not the Apple TV.
Have you tried playing back something you know has worked previously? Yes, they all work just not the 4K I am attempting when I get this error.
Have you gone through the basic troubleshooting steps like optimize database and clean bundles? Yes, my server runs those tasks frequently.
When was the last time it worked? Never tried 4K on this till today. What has changed in your setup since then? N/A
Have you searched the error message and tried any of the potential fixes that other people have suggested who have had the same error? Yes. Topics are opened about this error all the time. For years. There is never any info. The topics are closed or just people like you asking for more info. Is there really no one that actually works on this product who can provide ANY support?!
OK, except now you’ve hijacked someone else’s thread instead of starting your own. So it’s categorized incorrectly, and you now haven’t provided some of the basics like your PMS, player, Synology and ATV versions, and your network setup.
Also helpful are logs (that you’ve looked at yourself first) and some media information about the file that is not working.
Again, whether it be from Plex staff or the community, without sufficient basic information to work with there’s only so much support can be provided.
First off… Why is your reply asking for more information marked as a “SOLUTION”?! It is not a solution, it is just an inquiry for more details. That is another major problem with this forum.
Secondly, I have not “hijacked” this thread. Or did you miss the OP’s reply from almost 2 months ago? Here it is for you “Would be nice if someone could actually help instead being captain obvious by closing a duplicate post and not giving any advice for a solution.”. Which is exactly what was done. My comment however was in an effort to keep the thread open, since there is no need to have a gazillion for the same error, and more so to hopefully get both of us a REAL solution.
Given that error message… Is there no FAQ of possible places to check? What it is related to? Nothing? We can’t just play uninstall and re-install and jump through all these hoops without knowing anything about the error itself. Codec? Transcode? Cache? Bug? That is where support from the actual devs would come in handy.
That said, any further information regarding the error message itself would be greatly appreciated. Thank you!
A) The post marked as a solution was marked by the OP, after their second request for help.
Jumping on a closed/solved thread is bad form. This post was referencing a a MacOS issue, as you said you are running a syno. Different factors come into play.
Lets start with you creating your own thread, properly tagging it, answering the standard questions the forum asks for, (version info) and please post your server logs too.
Once that is done we will take a look and see what assistance we can provide.
1 Like
I was just trying to help explain how to best set yourself up to actually try and get some help. I’m assuming OP came back and marked the thread as solved because they have since gotten it working, but just didn’t come back to provide an update or any details. When you posted in the thread, they got notified, and then came and marked it as solved since it no longer concerns them.
While the error message may be the same, practically all the other components are likely to differ, and that’s why you want to create your own thread that is categorized correctly. One of the main reasons for this, is depending on where it lands, different staff members will be monitoring and potentially responding. Another is so that you provide all the pertinent information to your ecosystem and the error as it pertains to you. Yet another would be so that you can mark it as Solved once it is working for you (instead of what happened here, which is OP came back and marked it as Solved, because it is their thread and not yours). It is actually often not helpful having one thread trying to deal with the same error for multiple people, especially in the cases of generic/ambiguous errors. The root cause could vary greatly from person to person.
I didn’t “jump on a closed/solved thread” because it wasn’t until after my comment. Nice try though.
Either help with the problem or don’t bother replying. I will ask again…
What specifically is this error message in relation to? Codec? Transcode? Cache? Bug? That is where support from the actual devs would come in handy. If you don’t have this information then just say so and I’ll wait for someone who does.
Thank you for the long winded pointless response. Either help with the problem or don’t bother replying. I will ask again…
What specifically is this error message in relation to? Codec? Transcode? Cache? Bug? That is where support from the actual devs would come in handy. If you don’t have this information then just say so and I’ll wait for someone who does.
We are trying to help. That particular message is one of the more generic messages. Without additional information we are unable to provide specific troubleshooting recommendations.
One of the key things in troubleshooting is the plex server logs those provide us with significantly more information and context than your simple error message you are seeing. I have seen this when a server just needs rebooted, or also the server database is corrupt. But without logs narrowing down the root cause is almost impossible.
Even actual devs don’t have a crystal ball and would need a bare minimum of the some of the information and items I outlined in my long winded pointless response(s). Which I took the time to type out because I was trying to help with the problem. However, I shan’t bother replying further since you don’t seem to consider my time or advice to be helpful .
Good luck buddy.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
