I am seeing this error after [Finally] updating my server to the latest version ( 1.27.2.5929).
Server was restarted @ 11:09am
Attempted tune channel 16.1 @ 11:10am (ERROR: Could not tune… occurred)
Note: Hauppauge WinTV-quadHD device works fine with WinTV software. It also works fine in Plex server v1.19.
Note: If I continue to try tuning a channel, I can occasionally see a success.
Note: the indicator light on tuner 1 on the Hauppauge device illuminates briefly before failing. This leads me to believe that at least some communication occurred successfully between the tuner and Plex.
So I thought there may be something wrong with my tuner. I downloaded the hdhomerun app for an xbox and it was able to view channels without an issue.
I have restarted the tuner, restarted Plex, deleted tuner from Plex and added back. Still getting those same messages in the tuner logs when using Plex.
It appears we have a problem when there is more than one vbox device
Your tune attempts for the dvb-t vbox 527d which is on 192.168.68.103 are being sent to the dvb-s vbox 59de dvr on 192.168.68.104
We need to reproduce the problem to troubleshoot - at the moment I am encountering an ssdp issue with the vbox devices and would need to surmount that before I can repro the problem
We do not support dvb-s anyway and at the moment and until we know the cause of the vbox dvr’s issue with multiple devices online, my only advice is remove the dvb-s device
I suggest doing
removing the dvb-s device from the network
deleting all dvr’s within plex media server server settings for Live TV and DVRs
adding the dvb-t dvr and going through setup for that dvr
It is possible that the database will have entries for the removed dvb-s DVR and we may need to purge the contents of the Plex Media Server database table media_provider_resources - we can look into that if you still have difficulties after the above steps
And with regards to having wifi + ethernet active interfaces on the DVR, we may not be able to handle that. So always ensure only the ethernet interface is enabled
Would like to see if the database table is ok now and if there is a different cause.
Could you download the database and send me the zip and also repeat the tuning test - best to start with a launch of Plex Media Server with debug logging enabled beforehand and capture logs for a failure
And as before - please let me have the mac address and IP address of the dvb-t live DVR
A weird one. Perhaps the database is corrupt. Its just the DVB-T box has disappeared. Its there on the network and can login to it, however Plex doesn’t see it. If I have the DVB-S connected to the network, Plex will then see the DVB-T box.
Any suggestions? Do you still want the Database? Is there a way to start fresh and rebuild it?
Without the debug server logs and the database, I am blind to your issues
To help resolve the issue, please let me have the database, the debug server logs showing the issue when the dvb-s DVR is not configured and not on the network and full details of ethernet mac addresses and IP addresses of all the vbox dvrs and confirmation the wifi interfaces are disabled on the vbox dvrs
I may need to edit the database and give it back to you to use - so please do not add any media to your server once you let me have the database and until I give it back to you and you run with it to recreate the dvb-t DVR setup - ensuring at all times that the dvb-s dvr is off the network (until we find out the underlying issue and be in a position to support multiple vbox dvrs)
Hi @SA2000, the Australian/New Zealand VBox tech support rep. has decided to split this problem away from the many other issues covered in this forum item into a separate issue: DVR turning issue for Sydney Australia
server-synology
I’ll set about resetting my VBox device and going through creating new server logs (debug logging) and screen captures as requested by @llo36 (new forum item: [DVR turning issue for Sydney
To resolve the issue for systems with 2 vbox dvr’s on the network, we need to amend the table until the cause of the problem is identified and fixed. So for the 2 vbox dvrs issue we need to ensure only one is on the same network and once we have that, then to manually edit the database table and remove the two entries relating to the other vbox dvr
For this thread. The VBox connection to Plex can only support one channel set per box. or the streams will fail. If you are running multiple boxes, make sure that they deliver separate channels, no duplicates, see the tuning sydney issue thread.
Plex does a call to the VBox, and if there are duplicate channels will fail. So each VBox must have its own set that is not duplicated on the other.
Example:
VBox 1
7 Sydney
10 HD
VBox 2
SBS
ABC
and so on. No duplicates. There may also be other issues with connecting multiple VBoxes to plex, but this is the rule from VBox’s side. In my tests, this has worked for our SAT and terrestrial setup to be delivered into the same plex server.
Hi guys,
I’ve been running plex with Xteve for a while now, but I just got a new problem. Plex doesn’t seem to send the request to Xteve anymore.
I tried rebooting, removing the DVR and relink it, nothing.
Any idea?
Thank you!
This would be appropriate for a new post., as this thread is dealing with a tuning issue, and this will only confuse it further. I suggest starting a new thread and posting your logs and data for the problem.
Yes, but that is largely a generic failure error. Without specific information it will only site to confuse this thread even further. Hence, a new thread specific to the Xteve is appropriate as it will assist you and others from going down a rabbit hole
Apart from that, we do have an issue with more than one vbox device on the network. This still needs to be investigated. Plex Media Server may end up using the wrong vbox IP address. Until this is resolved my advice is not to have more than one Vbox on the local network. When the issue arises, recovery is not easy and needs editing one of the tables in the Plex Media Server database
Yes - we do have an issue that needs to be investigated. I am currently held back on this because of SSDP issues relating to how the vbox DVR announces itself which I need to get resolved first
