ok great. Thanks again! (I have been trying to figure this out practically all day today.). Enjoy!
3 Likes
Will this work on TVmate?
@jgomez177 Hey bud, sorry to bother you on the weekend and all, but I wanted to see if you have had a moment to look at the new issue on Github? I noticed on my DNS server dash that the P4C container suddenly made 756K DNS queries and when I jumped into the log it was going crazy in an error loop so fast I couldn't read it. I restarted the container and it doesn't work any more. Reinstalling it (I'm on Unraid FWIW) didn't fix it. It had been great for months. Here's what the container shows now at launch:
[INFO] Initializing Scheduler
⇨ http server started on [::]:7777
[INFO] Running EPG Scheduler
New token for us_west generated at 2025-02-01 03:14.25 +0000
(None, 'Error Exception type: ConnectionError')
Error running initial task: 'NoneType' object is not subscriptable
1 Like
Try changing to local it worked for me when west did not.
Pluto may have changed something.
I'm running Pluto for Channels v1.20 and PLUTO_CODE=local,us_east,us_west is still working for me.
2025-02-01T23:20:20.664400198Z [INFO] Running EPG Scheduler
2025-02-01T23:20:20.913926584Z New token for local generated at 2025-02-01 23:20.20 +0000
2025-02-01T23:20:21.402073645Z Retrieving local EPG data for 2025-02-01T23:00:00.000Z
2025-02-01T23:20:23.607566811Z Retrieving local EPG data for 2025-02-02T11:00:00.000Z
2025-02-01T23:20:25.691604365Z Retrieving local EPG data for 2025-02-02T23:00:00.000Z
2025-02-01T23:20:59.142482161Z New token for us_east generated at 2025-02-01 23:20.58 +0000
2025-02-01T23:20:59.542972750Z Retrieving us_east EPG data for 2025-02-01T23:00:00.000Z
2025-02-01T23:21:01.647878120Z Retrieving us_east EPG data for 2025-02-02T11:00:00.000Z
2025-02-01T23:21:03.945452180Z Retrieving us_east EPG data for 2025-02-02T23:00:00.000Z
2025-02-01T23:21:38.853653503Z New token for us_west generated at 2025-02-01 23:21.38 +0000
2025-02-01T23:21:39.282148497Z Retrieving us_west EPG data for 2025-02-01T23:00:00.000Z
2025-02-01T23:21:42.049055136Z Retrieving us_west EPG data for 2025-02-02T11:00:00.000Z
2025-02-01T23:21:44.373446408Z Retrieving us_west EPG data for 2025-02-02T23:00:00.000Z
2025-02-01T23:22:19.763523580Z Retrieving local EPG data for 2025-02-01T23:00:00.000Z
2025-02-01T23:22:22.023449297Z Retrieving local EPG data for 2025-02-02T11:00:00.000Z
2025-02-01T23:22:24.441091127Z Retrieving local EPG data for 2025-02-02T23:00:00.000Z
2025-02-01T23:22:26.002299021Z Retrieving us_east EPG data for 2025-02-01T23:00:00.000Z
2025-02-01T23:22:28.230987885Z Retrieving us_east EPG data for 2025-02-02T11:00:00.000Z
2025-02-01T23:22:30.936793337Z Retrieving us_east EPG data for 2025-02-02T23:00:00.000Z
2025-02-01T23:22:33.180266955Z Retrieving us_west EPG data for 2025-02-01T23:00:00.000Z
2025-02-01T23:22:35.626966294Z Retrieving us_west EPG data for 2025-02-02T11:00:00.000Z
2025-02-01T23:22:37.884099620Z Retrieving us_west EPG data for 2025-02-02T23:00:00.000Z
2025-02-01T23:23:13.265027337Z [INFO] EPG Scheduler Complete
Yeah, that's the version I'm on I presume (latest). You did give me the idea to roll back to 1.18 and try that, and this is what I get (basically additional lines of error)
Traceback (most recent call last):
File "/app/pywsgi.py", line 308, in <module>
error = providers[provider].create_xml_file(pluto_country_list)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/pluto.py", line 527, in create_xml_file
root = self.read_epg_data(elem, root)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/pluto.py", line 396, in read_epg_data
for entry in resp["data"]:
~~~~^^^^^^^^
TypeError: 'NoneType' object is not subscriptable
Traceback (most recent call last):
File "/app/pywsgi.py", line 308, in <module>
error = providers[provider].create_xml_file(pluto_country_list)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/pluto.py", line 527, in create_xml_file
root = self.read_epg_data(elem, root)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/app/pluto.py", line 396, in read_epg_data
for entry in resp["data"]:
~~~~^^^^^^^^
TypeError: 'NoneType' object is not subscriptable
Initialize XML File for local
New token for local generated at 2025-02-02 00:07.44 +0000
(None, 'Error Exception type: ConnectionError')
Initialize XML File for ALL
Initialize XML File for local
New token for local generated at 2025-02-02 00:07.57 +0000
(None, 'Error Exception type: ConnectionError')
Initialize XML File for ALL
Are you running something like pi-hole or a DNS filter?
Try overriding the DNS server for the container (assuming it's running in bridge mode).
in the docker compose statement
Cloudflare
network_mode: "bridge"
dns:
- "1.1.1.1"
- "1.0.0.1"
or Google
network_mode: "bridge"
dns:
- "8.8.8.8"
- "8.8.4.4"
Docker command line
Cloudflare
--dns=1.1.1.1 --dns=1.0.0.1
Google
--dns=8.8.8.8 --dns=8.8.4.4
While there is an issue with the error handling and I will correct that in a subsequent release, the error iteself does seem to be specific with your DNS.
The DNS entry failing is a call to service-channels.clusters.pluto.tv
If you have experience working within a docker container, I would look at opening an ash shell into the container and check the nslookup from the container for the above entry
You and @chDVRuser are exactly right. I should've checked that - the message was just a little cryptic to me so I didn't read it as DNS error. Looks like OISD NSFW blocklist added service-channels.clusters.pluto.tv, images.pluto.tv, and boot.pluto.tv to their blocklist for some reason.
After whitelisting them I'm back in business. Thanks, fellas!
1 Like
Again that's partly my bad for not handling the error correctly to provide a better log of the issue, but glad you resolved
There's a reason why I don't bother using adguard or pihole on my server and I always add the server ip to the whitelist.
1 Like
I find it worth it for a number of other reasons, but to each their own.
I came across this article today. If/when this is fully implemented, it may require us to log in to Pluto with a registered account... Just a "heads-up"
Just like TUBI
1 Like
Yup. I get it. They don't offer these free services out of generosity and kindness to humanity. It's all about $$. If they can get you to set up an account, then, they can market directly to your email address. (or sell it to others)
One way around it is to use a throwaway email address just for streaming service accounts. You can filter all incoming mail directly to the trash... 
1 Like
I hope he will add it to the docker so we can log in.
I have an account.