Using the links from nocords, I discovered a new error:
invalid source url: open https://nocords.xyz/pluto/playlist.m3u: The filename, directory name, or volume label syntax is incorrect.
I'm afraid this may be happening because our network at home has been plagued with DNS errors on a daily basis.
Nevermind - it worked the next time I tried it.
It's been a couple years since I last used Pluto and I had no idea it had so many channels!
Anyway - Thanks all!
The link you used had a : at the end causing the error
The text file I created to document my efforts didn't have the colon after the m3u, so I think that's something that was added by the error string builder. My experience was pretty consistent with the kind of effects I'm familiar with from our DNS errors. There was just no "Retry" option in the Custom Channel builder and entering everything again worked the second time, thankfully.
BTW - I'm very appreciative of what you've done to make things so much easier for the Channels community. Thanks!
Your initial attempt failed because you typed john instead of jon
The "h" just jumped in there from muscle memory, lol. That's why I cut-and-pasted and kept a log after that hiccup. 
I just expanded on this a bit more for those looking for more detailed directions:
I had Pluto working fine on my Synology NAS for a long time, but recently I have stopped getting guide data. It is possible the loss of guide data coincided with changing some security settings on my NAS. Are there any ports that need to be forwarded for Pluto to work properly in Channels? If not, what would be the recommended troubleshooting steps to try to figure out why I'm not getting guide data anymore?
It appears to be the Pluto source as mine is missing guide data for many channels and no errors in my docker container log.
About half of the channel listings I have don't start until 2am tomorrow morning. Guide info missing until then. The other half have normal listings.
Had the container refetch from Pluto and the DVR refetch from the container and everything is back to normal. 
Check your docker container log.
When it grabs guide data it will show this. Any errors would display after these lines in the log.
[INFO] Grabbing EPG...
https://api.pluto.tv/v2/channels?start=2024-02-12%2000%3A00%3A00.000-0800&stop=2024-02-12%2006%3A00%3A00.000-0800
https://api.pluto.tv/v2/channels?start=2024-02-12%2006%3A00%3A00.000-0800&stop=2024-02-12%2012%3A00%3A00.000-0800
https://api.pluto.tv/v2/channels?start=2024-02-12%2012%3A00%3A00.000-0800&stop=2024-02-12%2018%3A00%3A00.000-0800
https://api.pluto.tv/v2/channels?start=2024-02-12%2018%3A00%3A00.000-0800&stop=2024-02-13%2000%3A00%3A00.000-0800
I'm also not seeing the issue you are describing (have +/-24hrs of guide data for every one of my stations), but I've also switched to the @joagomez Docker:
Thanks. I didn't realize there were different ones that used Docker.
No worries; it's like 4 days old!
Great work! Do you have this in copyable text format?
thanks
peter
I'm seeing this in the logs. What does this mean?
|2024-02-14 12:45:45|stdout|[INFO] Grabbing EPG...|
|2024-02-14 10:03:32|stdout| - - [14/Feb/2024:10:03:32 +0000] GET /epg.xml HTTP/1.1 200 11949075 - Mozilla/5.0 ChannelsDVR+XMLTV/1.0 -|
|2024-02-14 09:45:44|stdout|Last ran: Wed Feb 14 09:45:44 UTC 2024|
|2024-02-14 09:45:44|stdout|mv: can't rename '*epg.xml': No such file or directory|
|2024-02-14 09:45:44|stdout|mv: can't rename '*playlist.m3u': No such file or directory|
It means it didn't fetch any guide data from Pluto during that run.
You pasted the logs upside down (reverse chronologoical order). Look at the timestamps.
That's probably from an html dump of the logs in Synology Docker Station.
To see the error that caused it, you have to see what was logged before those two lines.
errors will appear here
|2024-02-14 09:45:44|stdout|mv: can't rename '*playlist.m3u': No such file or directory|
|2024-02-14 09:45:44|stdout|mv: can't rename '*epg.xml': No such file or directory|
|2024-02-14 09:45:44|stdout|Last ran: Wed Feb 14 09:45:44 UTC 2024|
|2024-02-14 10:03:32|stdout| - - [14/Feb/2024:10:03:32 +0000] GET /epg.xml HTTP/1.1 200 11949075 - Mozilla/5.0 ChannelsDVR+XMLTV/1.0 -|
|2024-02-14 12:45:45|stdout|[INFO] Grabbing EPG...|
A good fetch starts like this
2024-02-15T00:00:03.093774660Z [INFO] Grabbing EPG...
2024-02-15T00:00:03.117201760Z https://api.pluto.tv/v2/channels?start=2024-02-14%2016%3A00%3A00.000-0800&stop=2024-02-14%2022%3A00%3A00.000-0800
2024-02-15T00:00:03.140956768Z https://api.pluto.tv/v2/channels?start=2024-02-14%2022%3A00%3A00.000-0800&stop=2024-02-15%2004%3A00%3A00.000-0800
2024-02-15T00:00:03.143840046Z https://api.pluto.tv/v2/channels?start=2024-02-15%2004%3A00%3A00.000-0800&stop=2024-02-15%2010%3A00%3A00.000-0800
2024-02-15T00:00:03.145837091Z https://api.pluto.tv/v2/channels?start=2024-02-15%2010%3A00%3A00.000-0800&stop=2024-02-15%2016%3A00%3A00.000-0800
2024-02-15T00:00:09.775053797Z [DEBUG] Using api.pluto.tv, writing cache.json.
and ends like this
2024-02-15T00:00:38.465110026Z [SUCCESS] Wrote the EPG to epg.xml!
2024-02-15T00:00:38.489745331Z [SUCCESS] Wrote the M3U8 tuner to playlist.m3u!
2024-02-15T00:00:39.227440884Z Last ran: Wed Feb 14 16:00:39 PST 2024
If you use Portainer you can download the last 4 hours of the log to a file.
Or by using this docker command (and optionally redirect output to a file)
docker logs -t --since=4h pluto-for-channels 2>&1
I found one issue, which was that my Synology firewall was causing problems with Docker containers. I got that resolved, and now it looks like guide data is being downloaded, but for whatever reason I'm still not seeing any of that data in my guide. Here is the latest snippet from my logs, showing a successfull write to epg.xml:
| 2024-02-15 00:47:02 | stdout | Last ran: Thu Feb 15 00:47:02 UTC 2024 |
|---|---|---|
| 2024-02-15 00:47:02 | stdout | |
| 2024-02-15 00:47:01 | stdout | [SUCCESS] Wrote the M3U8 tuner to playlist.m3u! |
| 2024-02-15 00:47:01 | stdout | [SUCCESS] Wrote the EPG to epg.xml! |
| 2024-02-15 00:47:00 | stdout | [INFO] Adding instance of CBS News Texas 6pm |
| 2024-02-15 00:47:00 | stdout | [INFO] Adding instance of CBS News Texas 5pm |
| 2024-02-15 00:47:00 | stdout | [INFO] Adding instance of CBS News Texas 5pm |
| 2024-02-15 00:47:00 | stdout | [INFO] Adding instance of CBS News Texas 4pm |
| 2024-02-15 00:47:00 | stdout | [INFO] Adding instance of Latest Texas News & Headlines |
| 2024-02-15 00:47:00 | stdout | [INFO] Adding instance of Latest Texas News & Headlines |
My guide still looks like this though:
Delete and Recreate the guide database in Channels DVR
Or Reload M3U and then Redownload XMLTV on the Pluto source
I woke up this morning and my guide data was back. Apparently it just took a long time to sync up after I updated my firewall rules. That seems to have been the root cause of multiple Docker issues I was having.
Channels DVR will perform both the Reload M3U and Redownload XMLTV periodically as you defined in the settings. Daily updates happen sometime between 9-11am.
I have been unable to tune the Pluto CNN Headlines channel for some time now. I'm using @maddox's pluto-for-channels docker container. Most or all of my other Pluto channels work. And I am able to tune this channel directly on the Pluto website. Error from log below. Any ideas?
2024/02/21 17:40:40.444343 [ERR] Could not start stream for M3U-PlutoTV ch9563 CNN HEADLINES: M3U: Could not fetch playlist from cfd-v4-service-channel-stitcher-use1-1.prd.pluto.tv: GET: https://cfd-v4-service-channel-stitcher-use1-1.prd.pluto.tv/stitch/hls/channel/5421f71da6af422839419cb3/master.m3u8?advertisingId=&appName=web&appStoreUrl=&appVersion=unknown&architecture=&buildVersion=&clientTime=0&deviceDNT=0&deviceId=3d45a5dd-d10a-11ee-ae63-0011329a6dcf&deviceMake=Chrome&deviceModel=web&deviceType=web&deviceVersion=unknown&includeExtendedEvents=false&serverSideAds=true&sid=56ac3835-5910-4b61-9802-4a9c54357907&userId=: 401 Unauthorized
Switch to the @joagomez version as noted above. I'm not having any issue with that station on there:
