vod2pod-rss: Error (409) when parsing YouTube account or playlist
Brilliant work, this! Was really looking for a solution like this!
I just started the service on a Raspberry Pi, but I can’t get it to work. Every time I submit a YouTube account or playlist I get this error message:
2023-05-07T18:19:01.758Z ERROR [app] could not translate rss
2023-05-07T18:19:01.759Z ERROR [app] could not parse rss, reason: unable to parse feed: no root element
I’m not sure where to look to solve this issue, do you have an idea where I could start?
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 35 (18 by maintainers)
I was able to replicate your issue by setting an invalid youtube apikey, so my guess it was some problem related to that.
I should definitely try to improve error messaging to check if the apikey works though!
feel free to close the issue, or I will close it myself in a few days if the problem does not shows up.
Okay, I fixed it. In case anyone has the same problem:
The main issue was that I was using a 4 year old, unused Google developer project. I had created an API key at that time. I tried using that key and it didn’t work. I thought maybe the key is too old somehow and created a new key, which didn’t work either.
I had the right idea but my first solution was wrong. You need to create a whole new project or it will not work. Google sets the quotas for old, unused projects to zero. There are supposedly ways to reactivate an old project but creating a new one is faster and works as well.
So check if your daily requests quota has been set to zero if you are getting 403 “quota exceeded” errors.
I use the app daily for many feed with 30 minutes refresh and I never got hit. Weird, maybe they have some rules to dinamically adjust them? Don’t know. Anyway good that you found the issue, since it does not seem a problem with the app I will close the issue again, thanks for reporting back!
BTW you can also use an .env file, use the default docker-compose.yml from this repo and on the same folder of it do
It’s an alternative way to set the api keys that I use mostly so that I can keep the docker-compose.yml file from leaking my api key when developing 😝 but can be used by anyone too (maybe I’ll actually write it as the preferred way in the documentation later, it’s probably less error prone)