Ok, it should be working now.
I have no freaking clue why this stopped working after working for years without interruption. I know what I changed to fix it, but it makes absolutely no sense as to why that was throwing a "404" error page.
I'll look into it more tomorrow, but at least for now, it seems to be working. If not, please report back.
I tried that -- doesn't work for titles. 
As an update to this, Cloudflare at nocords.xyz is now blocking traffic associated with ALL DNS providers available through my VPN (i.e., including OpenDNS which previously worked) . I've had to switch to access nocords.xyz directly (through a split tunnel) and bypass my VPN for this altogether.
This may be the reason others are getting 0 channels for the PlutoTV setup using nocords.xyz
Actually, the problem is (or was) on this end and unrelated to VPN access.
There are some security/SSL settings at CF that were being periodically reset causing the site to go down and simply return a "404" message. I changed some of those CF settings today, so it should be working better now and hopefully the dropouts will stop.
Sorry for the inconvenience.
Hi. I was reaching out to see if someone might be able to help trouble shoot why I can't seem to access this through Channels but the m3u plays in VLC player.
I had switched internet providers to a local provider called Total Highspeed. Shortly after, I discovered I could not connect to Channels anymore. Well I was able to figure out that something about how they run things didn't allow me to connect. This week I called and discover they have a "public ip address" you can pay as an add-on to the service but was allowed to try to see if it helped. After doing that, I can now access Channels and my locals coming in through my HD-Home Run come in fine but yet I am still unable to pull in the Pluto TV Channels. I would appreciate if someone could help walk me through a troubleshoot because I would like to know if it's possible to get this to work with the added cost of paying for the public ip address.
You definitely don't need a pubic IP address.
Please go here https://whatismyipaddress.com/ and PM me back your IP Address and I can look to see if your ISP is blocked.
You can also just go to these links in a browser and see if they download the files. If that works, there's no reason it shouldn't work within Channels.
https://nocords.xyz/pluto/playlist.m3u
https://nocords.xyz/pluto/epg.xml
Thank you for responding. I went to that link and pm'd you my ip address. And yes it looks like I can download by clicking on both the m3u link and the epg link. As a matter of fact, the m3u I opened and it opened up within VLC and plays fine from what I can tell.
Before the ISP allowed access to the public IP address I couldn't even access Channels to try to get the Pluto plugin to work.
Honestly that sounds like a local network issue and not an ISP/VPN,e tc issue. You should always be able to connect to Channels locally on your network without a 'public ip'.
I don't know. I just know after switching ISP Providers I was unable to access Channels at all until they changed something to allow me access to a public IP address. Ever since this temporary change was made to test to see if it made a difference I've been able to connect to Channels again without doing anything different. However their setup works, they don't have access to public IP address and it's an addon that costs to utilize.
Probably because you got a new gateway/modem with the new provider and need to configure it (if possible) to match your old one.
DHCP reserved IP addresses for internal devices and remote access to your CDVR (if you use it).
No new modem. Same modem as I used with the old provider. I'm not trying to argue that they're right and anyone here is wrong. Just relaying what has been shared. Tech support has said Plex users have had trouble without this public IP address addon.
OK. Just sounds like they're selling snake oil.
If they said you need a "static Internet IP address" instead of a "dynamic Internet IP address", that would be different.
Seems to be a small ISP servicing MO/AR selling Fiber and WiFi Internet access to bring Internet to rural areas.
It is a fiber internet company. Yeah maybe so about the snake oil, but I don't understand why I couldn't connect to Channels DVR before they "added" the public IP address. I guess I'm not sure what you're suggesting to do either though.
Are you trying to connect "Remotely", or on your own local network?
If remotely, you need to port forward your router/gateway to your Channels DVR server.
If locally, you need to have the device used to connect to your Channels DVR server configured on the same subnet or VLAN as your Channels DVR Server.
It's local network so how do I attempt that?
Depends on your network topology.
Usually an internal router on your LAN connects to the Internet gateway/modem to the Internet.
On the router you setup DHCP IP reservations for your internal LAN servers and devices.
For instance
LAN - (192.168.0.1)Router(10.0.0.2) - (10.0.0.1)Gateway/Modem to Internet
CDVR Server(192.168.0.2) - (192.168.0.1)Router
CDVR Client(192.168.0.3) - (192.168.0.1)Router
On the router you setup DHCP IP reservations of 192.168.0.2 for your CDVR Server and 192.168.0.3 for your CDVR Client, and so on for other devices.
Using a netmask of 255.255.255.0 they're all on the same network 192.168.0.0/24 so don't need subnet routing to communicate with each other. Especially useful if broadcast discovery is being used.
I have this setup fully working with m3u and xml through jellyfin. However, it doesnt seem to import the channel numbers like other m3u lists I use. Looking deeper, it seems that jellyfin channel numbers are generated though m3u's by a tvg-chno"CHANNEL NUMBER" variable for each channel. The m3u's this generates create channel-number="CHANNEL NUMBER" variables. Is this something that is possible to change so that jellyfin recognizes the channel numbers from the m3u?
Pretty sure Channels DVR works with channel-number and falls back to tvg-chno, so either should work.
Perhaps you can convince the author of jellyfin to be just as flexible?
Or maybe this [RELEASE] Playlist Manager for Channels [Streaming Library Manager Extension] would work for you?
Rather than importing the channel numbers which can result in channel number conflicts, try using the starting channel number method.
The issue isnt the associated channel numbers (there is no number conflict), its the fact that jellyfin only displays the channel number if the channel has the tvg-chno variable (it seems like the channels produced for plutotv instead use the channel-number variable).