search

fpnewton / DailyWirePodcastProxy

RSS podcast proxy to add authenticated DailyWire podcasts to any podcast client.
MIT License
17 stars 1 forks source link

DailyWirePodcastProxy completely stopped working #37

Open samuelvisser opened 3 weeks ago

samuelvisser commented 3 weeks ago

This service worked great for me up until a little more than a week ago. I tried completely removing and re- installing the container but nothing worked.

Today I noticed the DW website UI quite drastically changed, which made me think they might have changed their backend too, causing their private API to break.

Am I the only one with this issue? And if not, is this project still maintained? I would love to have this working again

martinlumi commented 3 weeks ago

Mine has gone down too, unfortunately..

fpnewton commented 3 weeks ago

One problem is how I originally intercepted the login page via headless chrome. I don't run it in a container and I still have the same chrome version installed on my server, so it still runs for me (I just got a latest episode about an hour ago). I have some ideas for what needs to be done, so I'll start working on it soon.

samuelvisser commented 3 weeks ago

One problem is how I originally intercepted the login page via headless chrome. I don't run it in a container and I still have the same chrome version installed on my server, so it still runs for me (I just got a latest episode about an hour ago). I have some ideas for what needs to be done, so I'll start working on it soon.

Interesting, that sounds very promising! Really hope you get this working again i was VERY happy about this service

samuelvisser commented 3 weeks ago

The latest episode i see is the morning wire on the 25th of October. All evening shows that same day broke, those i have only until the 24th.

martinlumi commented 3 weeks ago

My logs suggest mine went down yesterday. It was a wall of text, but I had GPT analyse the error message:

This error suggests that there’s a misconfiguration issue with the dependency injection setup, specifically around the IGraphQLClient service, and it seems to be related to the Simple Injector and Microsoft.Extensions.DependencyInjection configurations. The error indicates that the program times out when attempting to retrieve IGraphQLClient, which may be related to either the network dependencies or the configuration of your DI (Dependency Injection) setup.

fpnewton commented 3 weeks ago

I would guess that your access token has expired, as that's been 99% of the cause of graphql errors. Try deleting the tokens.dat file to force it to login again.

samuelvisser commented 3 weeks ago

My logs suggest mine went down yesterday. It was a wall of text, but I had GPT analyse the error message:

I have the same error messages, also about IGraphQLClient

martinlumi commented 3 weeks ago

I would guess that your access token has expired, as that's been 99% of the cause of graphql errors. Try deleting the tokens.dat file to force it to login again.

I always delete tokens.dat when it goes down, but this time it doesn't take. image

martinlumi commented 2 weeks ago

@samuelvisser Have you managed to make it work again? I've done a fresh install, tried both Linux and Windows versions, but same error on all.