Server Version#: 1.21.1.3830 Player Version#: 4.47.3 I am trying to use my xTeVe-like proxy as a tuner in order to be able to watch my IPTV in Plex. However, I am unable to get pass this error which shows up whenever I select my tuner (even before clicking on Scan channels), see screenshot. [er…

So a bit confused, are you saying you are writing your own app or using xteve? If you need basic auth, you should be able to add the auth to each of your playlist urls that you import in to xteve. Typically you would download the playlist your from your provider for your account and it should alrea…

Sorry for the confusion, I mentioned xTeVe-like app to help set up the context here, but it kinda backfired. I am writing my own tuner as the xTeVe API seemed very simple. I cannot use xTeVe because I need basic auth to fetch access token for bearer token (sry, that last part didn’t make it to my p…

OK, gatcha. Now I have not dug in to the code so I may be off base. Did you write your code to allow Plex to find it automatically on the network? I did notice that xteve is discovered and always starts off on port 80 not the 34400. So I assume that the initial request on port 80 may be what your mi…

Well, as I said, it’s all running on one port (3000 by default but configurable) and it has a /discover.json endpoint, which I suppose handles the initial discovery of the tuner in the PMS. This works neatly and I even have /* endpoint which catches every non-specified route, logs the request and r…

ok i decided to look it to this and you are missing some info in your discover.json so I am not sure if it is needed or not. The other thing is that you are not escaping your json strings and is probably your biggest problem so you may want to read up on that. Here is what the discover.json is from…

I believe my discover.json posted above has all this info, I reformatted it to be more clear but all the fields are there. Where do you see not escaped strings? Anyway, million thanks for looking into this.

lol, sorry the forum removed the escapes in the post. Your / should be \/ in your URLs. http:\/\/127.0.0.1:3000\/discover.json Since the forum cleaned this up I am not sure you are doing this.

Please excuse me jumping in? You can use code format bracketing to preserve things: ``` (back-tick / grave character) will preserve \ when entered ``` Looks like: will preserve \ when entered

Hmm, I will get to verify this tomorrow, but I don’t think this will be the issue, as I copied all the responses from xTeVe to see the payload and structure and there were no escaped characters, I am 120% sure. But I will try it to be really really sure. From my POV, it looks like PMS received an em…

hmm, I just pulled the discover.json from xteve that I have setup and you are correct, it is not being escaped. This is what I got from xteve. http://192.168.0.59:34400 1 0 urn:schemas-upnp-org:device:MediaServer:1 xTeVe Silicondust HDTC-2US HDTC-2US uuid:2020-08-OGEU-YV7KEO:5

Unable to use tuner - problem getting channels from my IPTV

Plex Media Server

johnm_ColaSC January 8, 2021, 1:38pm 16

Plex does not officially support third part emulation of a tuner device. I have retagged your post with the other-third-party tag. You might find other user support in the xTeVe - IPTV for Plex DVR thread.

Topic		Replies	Views
Plex won't find channels Live TV & DVR livetv-dvr , server-windows	30	3650	April 26, 2021
Unable to tune to channel (again, more research now) Plex Media Server livetv-dvr , server-windows	88	2460	July 17, 2019
Could not tune channel. Please check your tuner or antenna Live TV & DVR server-windows	436	19285	November 7, 2025
"Could not tune channel. Please check your tuner or antenna." Error Live TV & DVR livetv-dvr , server-windows	115	16816	October 1, 2020
Live TV no longer works Live TV & DVR server-linux	16	321	December 20, 2020

Unable to use tuner - problem getting channels from my IPTV

Related topics