Server Version#: 1.42.1.10054
Player Version#: 4.147.1
Tuner Make/Model: SiliconDust HDHomeRun Flex Quattro
Hi,
I have an issue getting my new HDHomeRun Flex Quattro working in Plex. When I try and play anything from the guide, it says Playback Error, could not tune channel.
I’ve included the screenshots of this and the HDHomeRun configured in Plex. The HDHomeRun is on the network and accessible.
It works fine from the Channels app on my AppleTV.
Is this iOS/tvOS?
I am having the same issue. It has happened the last two mornings. I have fixed it by reinstalling the Plex server app. It works fine all day. In the morning, same issue.
Any thoughts on fix? First time it’s ever done this.
That’s on the web client. On iOS I just get a spinning circle.
Same issue here. Get the error on web client - AppleTV just spins with nothing happening. HDHomeRun app works fine, no issues.
I am having the same issue. The HDhomerun app shows all the channels on my tuner, but plex isn’t hooking in correctly anymore. This just started happening recently. I noticed some stuff I had set to record to DVR didn’t record, and then when I checked, it wasn’t connecting to channels.
I uninstalled and re-installed the DVR, and now it doesn’t error, but the channels will not load in.
Resetting the DVR appears to have fixed it, but it is being very buggy and slow.
Same problem here. I’m not able to play TV on plex web. My iOS app does nothing but a spinning wheel. Over the years there have been several of these threads and all were closed without any solution or suggestions. I’ve tried deleting and reinstalling the DVR. Nothing seems to work. I can reach my HDHomeRun via the web interface. The signal strength is 100%. It seems to be something in the transcoding, but I have no way to diagnose anything. Sorry, I meant encoding not transcoding.
Click on the cog for the tuner and make sure you have Convert Video While Recording set to Off and Use hardware-accelerated video encoding unchecked.
Under server settings > Transcoder
Enable HEVC video Encoding (experimental) Never or HEVC sources only.
Probably because they were just a bunch of “me too” posts with no real information or missing the server logs zip file.
You’re probably right.
New information from my problem. If I hit record, the program records just fine and can be watched after recording. I’ve tried turning off hardware-accelerated encoding and making sure convert video while recording is turned off. No change. I can record and watch later, but still cannot watch live.
You either don’t have enough CPU (low power NAS) or some other setup issue, but without logs this will go nowhere.
I’ve collected logs. What do I post and how do I post them? I guarantee it isn’t a CPU/low powered NAS problem as the issue just started recently. When I watch the CPU utilization with Plex running, I’m at about a 3% load.
I’ve tried recording, but for me that doesn’t even work. Same issue. I’ve also changed the settings to match what was suggested.
Logs here.
@jranck
At your convenance:
Go to Server Settings > General and uncheck Enable Plex Media Server verbose logging
Verbose logging is only useful to debug specific issues and should only be enabled if requested by support staff
It just made it harder to see what was going on.
This is said in “General” and not to any one particular person.
Since the introduction of the “Remote Watch” pass, Plex is a little more picky about network connections from clients. If you are having issues with the “New Experience” clients then you will have to validate that you do not have DNS problems. (If you are using docker then you need to check from within the container.)
Check logs for these conditions:
Your server has to be claimed with a working CERT.
DEBUG - CERT: incomplete TLS handshake from [::ffff:x.x.x.x]:57015: Connection reset by peer
WARN - [CERT/OCSP] getCertInfo failed; skipping stapling
Your router and ISP can’t modify the DNS request for your server.
nslookup plex.tv should return at least two addresses
Your router can’t block DNS rebinding for plex.direct and should return an address for your servers CERT
Network: xx-xx-xx-x.abcdefghijklmnopqrstuvwxyz012345.plex.direct failed to resolve to xx.xx.xx.xx but instead yielded (null)
Too many failed Cert requests will cause your server to be blocked by Plex.
Last thing would be codecs and the transcoder with regard to the DVR:
Android Mobile and IOS clients no longer have mpeg2 decode ability so everything gets transcoded to h.264 unless you set it for HEVC which I don’t recommend. Decode will always be software which hits the CPU hard and is a bummer for NAS users. Hopefully they will finish up the FFMPEG upgrade to 6.1, break a bunch of stuff and then work on the Transcoder.
New logs without verbose logging here:
Plex Media Server Logs_2025-08-21_11-52-49.zip (3.5 MB)
One more thing. We use Apple TV with the Plex app to stream from our local media server to our TV. I can watch live TV through the Apple TV.
AFAIK, Apple TV doesn’t have the new experience and still allows non ssl communication with the Plex server.
Verbose is till active, I see where I dropped the last step that you have to restart your server after saving the setting.
Local DNS is not resolving your server.
DNS-Rebinding protection is active.
Remote Access is configured but not working.
I respect peoples right to use their server their way, but you should at least ensure that any tunnels, reverse proxies, addons etc are configured properly and most importantly disclose them. This is the primary reason Plex employees won’t even comment on a thread, it’s like walking into a minefield. Ultimately if your networking isn’t working it is a user problem.
