ESPN+ & FOX Sports with Custom Channels via EPlusTV

Give it some time. Disney will eventually stop the streams.
If the apps are gone, there is really no reason to keep paying for streams. A few channels users aren't going to make a huge difference.
enjoy the streams while they work and if it continuesk, great if it doesn't, i guess time to move to other alternatives.

1 Like

…because the Ocho isn’t a real linear channel.

1 Like

Actually, I doubt this very much. Disney is just consolidating their platforms.

In there eyes those apps became redundent next to Hulu and Disney+. The latter of which has been rumored to be getting linear channels in the near future.

Their press release expressly sent users to the site to continue to enjoy the feeds and content if you had access.

This is different than Paramount closing their apps and feeds. They were trying to cut costs to make a deal to be purchased happen.

They also do not own a tv provider like Hulu Live to consolidate the linear channels into. Yes they had Paramount+, but they would have had to retool it to support both standalone and tv provider logins, which would have taken too long given the pending sale negotiations.

This is different, until Disney sells the ABC and ESPN family of networks.

2 Likes

It's real if you believe it m0ng31 we believe , or could at least teach us how you scrape your guide data?

image

It would just be funny to have it work :smiley:

Been trying to get started with ESPN+ using eplustv and I have a docker container running but getting refresh token errors when starting - here's the first few lines of the log:

2024-09-24 14:25:34 
2024-09-24 14:25:34 > [email protected] start
2024-09-24 14:25:34 > ts-node index.ts
2024-09-24 14:25:34 
2024-09-24 14:25:36 === E+TV v3.2.1 starting ===
2024-09-24 14:25:37 === ESPN+ Auth ===
2024-09-24 14:25:37 Please open a browser window and go to: https://www.espn.com/watch/activate
2024-09-24 14:25:37 Enter code:  xxxxxx
2024-09-24 14:26:31 Refreshing device token (ESPN+)
2024-09-24 14:26:31 Could not get device token exchange
2024-09-24 14:26:31 Refreshing device refresh token (ESPN+)
2024-09-24 14:26:31 AxiosError: Request failed with status code 400
2024-09-24 14:26:31     at settle (/app/node_modules/axios/lib/core/settle.js:19:12)
2024-09-24 14:26:31     at IncomingMessage.handleStreamEnd (/app/node_modules/axios/lib/adapters/http.js:512:11)
2024-09-24 14:26:31     at IncomingMessage.emit (node:events:529:35)
2024-09-24 14:26:31     at IncomingMessage.emit (node:domain:489:12)
2024-09-24 14:26:31     at endReadableNT (node:internal/streams/readable:1400:12)
2024-09-24 14:26:31     at processTicksAndRejections (node:internal/process/task_queues:82:21) {
2024-09-24 14:26:31   code: 'ERR_BAD_REQUEST',
2024-09-24 14:26:31   config: {
2024-09-24 14:26:31     transitional: {
2024-09-24 14:26:31       silentJSONParsing: true,
2024-09-24 14:26:31       forcedJSONParsing: true,
2024-09-24 14:26:31       clarifyTimeoutError: false
2024-09-24 14:26:31     },
2024-09-24 14:26:31     adapter: [ 'xhr', 'http' ],
2024-09-24 14:26:31     transformRequest: [ [Function: transformRequest] ],
2024-09-24 14:26:31     transformResponse: [ [Function: transformResponse] ],
2024-09-24 14:26:31     timeout: 0,
2024-09-24 14:26:31     xsrfCookieName: 'XSRF-TOKEN',
2024-09-24 14:26:31     xsrfHeaderName: 'X-XSRF-TOKEN',
2024-09-24 14:26:31     maxContentLength: -1,
2024-09-24 14:26:31     maxBodyLength: -1,
2024-09-24 14:26:31     env: { FormData: [Function], Blob: [class Blob] },
2024-09-24 14:26:31     validateStatus: [Function: validateStatus],
2024-09-24 14:26:31     headers: AxiosHeaders {
2024-09-24 14:26:31       Accept: 'application/json',
2024-09-24 14:26:31       'Content-Type': 'application/x-www-form-urlencoded',
2024-09-24 14:26:31       Authorization: 'Bearer xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx',
2024-09-24 14:26:31       'User-Agent': 'axios/1.2.2',
2024-09-24 14:26:31       'Content-Length': '617',
2024-09-24 14:26:31       'Accept-Encoding': 'gzip, compress, deflate, br'
2024-09-24 14:26:31     },

I am able to get a channels.m3u and xmltv.xml files and I'm able to kinda use them - the stream won't play and I get errors in the log like:

2024-09-24 16:51:42 Channel #1 has an active event (The Pat McAfee Show). Going to start the stream.
2024-09-24 16:51:42 Could not get device token exchange
2024-09-24 16:51:42 Could not get device token exchange
2024-09-24 16:51:42 Could not get account grant
2024-09-24 16:51:42 Could not get BAM access token
2024-09-24 16:51:42 Event status:  OVER
2024-09-24 16:51:42 Could not get stream data. Event might be upcoming, ended, or in blackout...
2024-09-24 16:51:42 Failed to parse the stream
2024-09-24 16:51:42 Could not get a playlist for channel #1. Please make sure there is an event scheduled and you have access to it.

Looking at the schedule it's not over and I think this error is happening only because of the token issues above, any suggestions / help?

1 Like

Did you go to ESPN and login with that activation code?

Yes and the page refreshed saying that the device is activated.

Try to find the file folder espn_plus_tokens.json and delete it. Recreate the container. Follow the logs to reauthorize and get a new token.

I've seen this happen before when using a VPN

1 Like

You're right, the computer running this container is on a VPN but I thought that might be necessary to avoid ESPN+ blackout regional issues. I'll set this up on a different machine if not the case!

Yeah ESPN+ doesn't really play nice with VPNs, so I'd try it on a different box if you're able to

1 Like

yep! That solved all the issues, thanks a ton.

Most importantly, thank you for the amazing work!

Not entirely sure if this should be posted here or a new thread all-together. The problem I've encountered is that when piped into plex via threadfin, stream is dropped when a commercial starts. No issue when played via channels or with vlc via channels.m3u. Appreciate any guidance. Thanks again!

This is most likely caused by the #EXT-X-DISCONTINUITY-SEQUENCE tag in the m3u8 file that'll happen on commercial breaks

Plex is pretty suboptimal. Either use channels or nextpvr

Any updates on whether we'll get 4K college football? Or is that something that Fox broke with the API?

Seconded! Looks like chrome capture on HDMI capture may be only way

I just looked at this, and funnily enough it's using DRM

I'm not seeing any upcoming ones on the schedule: https://support.fubo.tv/hc/en-us/articles/360011483011-What-events-in-4K-HDR-are-coming-up-on-Fubo

DirectTv confirms the next college football 4K game is not until October 12th

https://www.directv.com/insider/top-sporting-events-in-4k/

Inaccurate. 4k on direct tv stream tomorrow



1 Like