Schedules Direct Guide Data No Longer Working - Country/Regions listed as "Undefined" in the setup guide is broken.

[junobomb]

This issue respects the following points:

• This is a bug, not a question or a configuration issue; Please visit our forum or chat rooms first to troubleshoot with volunteers, before creating a report. The links can be found here.
• This issue is not already reported on GitHub (I've searched it).
• I'm using an up to date version of Jellyfin Server stable, unstable or master; We generally do not support previous older versions. If possible, please update to the latest version before opening an issue.
• I agree to follow Jellyfin's Code of Conduct.
• This report addresses only a single issue; If you encounter multiple issues, kindly create separate reports for each one.

Description of the bug

SchedulesDirect: request that a Jellyfin developer contact me

I'm the developer that created and manage the JSON service at SchedulesDirect. Can someone from Jellyfin please contact me regarding an issue between the Jellyfin client and the SchedulesDirect service?I can be reached at rkulagow @ schedulesdirect.org Thanks. -- SchedulesDirect: request that a Jellyfin developer contact me [rkulagow](https://forum.jellyfin.org/u-rkulagow) Online

Junior Member

Posts:1
Threads:1
Joined:2024 Dec
Reputation:0
Country:United States
#1Yesterday, 08:58 PM
Hi -

I'm the developer that created and manage the JSON service at SchedulesDirect. Can someone from Jellyfin please contact me regarding an issue between the Jellyfin client and the SchedulesDirect service?

I can be reached at rkulagow @ schedulesdirect.org

Thanks.

Reproduction steps

Schedules Direct - program data is broken and all of the Country/Regions are "Undefined"

What is the current bug behavior?

"Underfined" Coutry Region under Schedules Direct guide setup as well as no guide data.

What is the expected correct behavior?

Guide Data

Jellyfin Server version

10.10.0+

Specify commit id

No response

Specify unstable release number

No response

Specify version number

No response

Specify the build version

10.10.3

Environment

- OS:
- Linux Kernel:
- Virtualization:
- Clients:
- Browser:
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- GPU Model:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

at Jellyfin.LiveTv.Listings.SchedulesDirect.Request[T](HttpRequestMessage message, Boolean enableRetry, ListingsProviderInfo providerInfo, CancellationToken cancellationToken, HttpCompletionOption completionOption)
   at Jellyfin.LiveTv.Listings.SchedulesDirect.GetTokenInternal(String username, String password, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.Listings.SchedulesDirect.GetToken(ListingsProviderInfo info, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.Listings.SchedulesDirect.GetProgramsAsync(ListingsProviderInfo info, String channelId, DateTime startDateUtc, DateTime endDateUtc, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.Listings.ListingsManager.GetProgramsAsync(ChannelInfo channel, DateTime startDateUtc, DateTime endDateUtc, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.DefaultLiveTvService.GetProgramsAsync(String channelId, DateTime startDateUtc, DateTime endDateUtc, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.Guide.GuideManager.RefreshChannelsInternal(ILiveTvService service, IProgress`1 progress, CancellationToken cancellationToken)
[2024-12-02 20:46:34.133 +00:00] [ERR] [43] Jellyfin.LiveTv.Listings.SchedulesDirect: Request to https://json.schedulesdirect.org/20141201/token failed with response "{\"response\":\"ACCOUNT_DISABLED\",\"code\":4005,\"serverID\":\"20141201.web\",\"message\":\"Account has been disabled. Please contact Schedules Direct support: service@schedulesdirect.org for more information.\",\"token\":\"CAFEDEADBEEFCAFEDEADBEEFCAFEDEADBEEFCAFE\",\"datetime\":\"2024-12-02T19:44:23Z\"}"
[2024-12-02 20:46:34.133 +00:00] [ERR] [43] Jellyfin.LiveTv.Guide.GuideManager: Error getting programs for channel "BABY FIRST TV"
System.Net.Http.HttpRequestException: Request failed: Forbidden
   at Jellyfin.LiveTv.Listings.SchedulesDirect.Request[T](HttpRequestMessage message, Boolean enableRetry, ListingsProviderInfo providerInfo, CancellationToken cancellationToken, HttpCompletionOption completionOption)
   at Jellyfin.LiveTv.Listings.SchedulesDirect.GetTokenInternal(String username, String password, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.Listings.SchedulesDirect.GetToken(ListingsProviderInfo info, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.Listings.SchedulesDirect.GetProgramsAsync(ListingsProviderInfo info, String channelId, DateTime startDateUtc, DateTime endDateUtc, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.Listings.ListingsManager.GetProgramsAsync(ChannelInfo channel, DateTime startDateUtc, DateTime endDateUtc, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.DefaultLiveTvService.GetProgramsAsync(String channelId, DateTime startDateUtc, DateTime endDateUtc, CancellationToken cancellationToken)
   at Jellyfin.LiveTv.Guide.GuideManager.RefreshChannelsInternal(ILiveTvService service, IProgress`1 progress, CancellationToken cancellationToken)
[2024-12-02 20:46:34.156 +00:00] [ERR] [38] Jellyfin.LiveTv.Listings.SchedulesDirect: Request to https://json.schedulesdirect.org/20141201/token failed with response "{\"response\":\"ACCOUNT_DISABLED\",\"code\":4005,\"serverID\":\"20141201.web\",\"message\":\"Account has been disabled. Please contact Schedules Direct support: service@schedulesdirect.org for more information.\",\"token\":\"CAFEDEADBEEFCAFEDEADBEEFCAFEDEADBEEFCAFE\",\"datetime\":\"2024-12-02T19:44:23Z\"}"
[2024-12-02 20:46:34.156 +00:00] [ERR] [38] Jellyfin.LiveTv.Guide.GuideManager: Error getting programs for channel "BABY TV"
System.Net.Http.HttpRequestException: Request failed: Forbidden
   at Jellyfin.LiveTv.Listings.SchedulesDirect.Request[T](HttpRequestMessage message, Boolean enableRetry, ListingsProviderInfo providerInfo, CancellationToken cancellationToken, HttpCompletionOption completionOption)

FFmpeg logs

Client / Browser logs

No response

Relevant screenshots or videos

No response

Additional information

No response

[junobomb]

https://forum.jellyfin.org/t-schedulesdirect-request-that-a-jellyfin-developer-contact-me

[joshjones1980]

Thank you for posting this, Junobomb; I came here to do the same.

Obviously, I too am experiencing this issue.

[anthonylavado]

We responded on the forum thread, we're aware and are looking into it.

[rkulagowski]

(I'm the SchedulesDirect JSON developer.)

It appears that something within Jellyfin is caching old tokens, and then presenting them, even after the token has expired. That trips our fraud system, and therefore is blocking Jellyfin users.

Here's what an example log looks like:

|2024-12-01T05:19:18Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:18Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:18Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:19Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:22Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:22Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:22Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:22Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:22Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:27Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:27Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:27Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:28Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:29Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:34Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:34Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:34Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:34Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8
|2024-12-01T05:19:34Z|check_for_valid_token(24.3.175.118):client sent old token.|token:0fe0a83c70b5f4971ce87990bc12a7d8

(etc)

So multiple times per second, this particular IP address was connecting to the service with a stale token.

If I lookup that 0fe0.... token, it was issued to a user on: 2024-11-23 05:04:02

However, when I check the current token which that user has been granted, it was generated on 2024-12-01 05:04:02

Something inside of Jellyfin is presenting old tokens, and because those tokens aren't current, the requests are getting rejected and that causes the account lock out.

In addition, when Jellyfin presents the old token, the response from our API is an error, code 4003: "Invalid username or token has expired." But it looks like Jellyfin is ignoring that error; when it gets code 4003 Jellyfin should request a new token and then use it.

If there's multiple processes involved in a Jellyfin system (grabbing images? refreshing celebrity data?), at least one of them seems to not realize that the token has been rotated; a token is only valid for 24 hours or until a new token is requested.

The above is just a single user; our fraud detectors are seeing this for over 500 Jellyfin clients, so it's 1000's of requests per second.

[socphoenix]

Rkulagowski, were you seeing this before the most recent update? I tried rolling back the most recent upgrade before this GitHub issue went live and it didn’t fix the failure to pull data from schedules direct.

[greyspace07]

socphoenix, did you check the Jellyfin log after you rolled back for any reference to schedulesdirect token? The error in my log has changed from a bad token (deadbeef) and looks to be pointing to my SD account being disabled/locked. I tried to pull an XMLTV file from SD as a workaround until this issue is fixed, but got rejected. I think JF is causing all of our SD accounts to get disabled. Just a thought... I deleted my LiveTV schedules config and hope my account resets after a period.

[kevinnord]

Rkulagowski, were you seeing this before the most recent update? I tried rolling back the most recent upgrade before this GitHub issue went live and it didn’t fix the failure to pull data from schedules direct.

I am still using JFin 10.9.11 and I am experiencing the same issue. I haven't upgraded at all (so no rollback). I've experienced the same outage for about two days.

[kevinnord]

socphoenix, did you check the Jellyfin log after you rolled back for any reference to schedulesdirect token? The error in my log has changed from a bad token (deadbeef) and looks to be pointing to my SD account being disabled/locked. I tried to pull an XMLTV file from SD as a workaround until this issue is fixed, but got rejected. I think JF is causing all of our SD accounts to get disabled. Just a thought... I deleted my LiveTV schedules config and hope my account resets after a period.

I'm not the person you asked, but I found this thread while troubleshooting a s imilar issue. These are the most recent logs I have, hope they help shed some light for tohers:

[2024-12-04 12:34:34.182 +00:00] [ERR] Error adding metadata
System.ArgumentNullException: Value cannot be null. (Parameter 'listingsId')
at System.ArgumentNullException.Throw(String paramName)
at System.ArgumentNullException.ThrowIfNull(Object argument, String paramName)
at System.ArgumentException.ThrowNullOrEmptyException(String argument, String paramName)
at Jellyfin.LiveTv.Listings.SchedulesDirect.GetChannels(ListingsProviderInfo info, CancellationToken cancellationToken)
at Jellyfin.LiveTv.Listings.ListingsManager.GetEpgChannels(IListingsProvider provider, ListingsProviderInfo info, Boolean enableCache, CancellationToken cancellationToken)
at Jellyfin.LiveTv.Listings.ListingsManager.AddMetadata(IListingsProvider provider, ListingsProviderInfo info, IEnumerable1 tunerChannels, Boolean enableCache, CancellationToken cancellationToken) at Jellyfin.LiveTv.Listings.ListingsManager.AddProviderMetadata(IList1 channels, Boolean enableCache, CancellationToken cancellationToken)

EDIT TO ADD: with regard to JFin causing accounts to be loced at SD: I am able to log in to the SD webpage and my status shows as "active", so I am not sure if that is the cause. Far from an expert but happy to help with logs or testing.

[davew723]

I'm observing the same issue with 10.10.3. I also confirmed my schedules direct account if valid. All country codes in jellyfin settings are also listed as undefined. The root of my problem looks to be this...

[2024-12-04 12:57:02.560 +00:00] [ERR] [22] Jellyfin.LiveTv.Listings.SchedulesDirect: Request to https://json.schedulesdirect.org/20141201/token failed with response "{\"response\":\"ACCOUNT_DISABLED\",\"code\":4005,\"serverID\":\"20141201.web\",\"message\":\"Account has been disabled. Please contact Schedules Direct support: service@schedulesdirect.org for more information.\",\"token\":\"CAFEDEADBEEFCAFEDEADBEEFCAFEDEADBEEFCAFE\",\"datetime\":\"2024-12-01T21:19:19Z\"}"
[2024-12-04 12:57:02.562 +00:00] [ERR] [22] Jellyfin.Api.Middleware.ExceptionMiddleware: Error processing request. URL "GET" "/LiveTv/ListingProviders/Lineups".
System.Net.Http.HttpRequestException: Request failed: Forbidden

... Interesting that it reporting my token as CAFEDEADBEEF. That seems like some debug value not the real SHA1 token. I haven't had much time to dig into the problem this morning. I do see that string in the Jellyfin test code but I don't really see it in the normal code paths. So I'm assuming the SD service is returning this instead of the token we provided. Of JF is passing something really bad.

[greyspace07]

Yep, I'm seeing/seen exactly what you both sent. Initially, I was seeing the classic fake-hex DEADBEEF token and now the cancellation token error. Interesting that this stopped working for some users who haven't upgraded in the last few weeks, if I'm reading that correctly.
I also see my SD account as active, and I found a test URL in a support page for SD which behaved as though I'm not blocked. But I'm getting a 4005 account disabled back from SD when I try to pull an XMLTV file. If that helps anyone with a lot more skills than I have.

[jeff-gooch]

EDIT TO ADD: with regard to JFin causing accounts to be loced at SD: I am able to log in to the SD webpage and my status shows as "active", so I am not sure if that is the cause. Far from an expert but happy to help with logs or testing.

I can confirm that the account block is with SD, as attempting to connect via EPG123 instead of JF produces a failed login message with the same ACCOUNT_DISABLED error.