If the linear feed fails again, before you do anything, can you send me a DM with all the NFL tokens?
Still not sure about the original linear feed failure, but I figured out why my subsequent container rebuild wasn't pulling any events: I had just cancelled my plan's renewal, although the plan still works at the web site up to the expiration date.
I just opened a pull request with a fix. Feel free to DM me if you need more info.
1 Like
Unfortunately the Disney+ feeds of the ESPN content is all using Playready DRM 
1 Like
I have version 4.1.0 installed, how can I update to the new version? I'm on Ubuntu 20.
Depends on how you set it up originally
I've updated OliveTin-for-Channels Project One-Click to support v4.1.7+ of E+TV, with its reduced set of environment variables and webUI. Complete the few required fields, and click -- the E+TV container will be created for you in Portainer-Stacks, along with a CDVR Custom Channels Source:
3 Likes
I'm curious, @bnhf: if you set LINEAR_CHANNELS to true, will it create 2 sources on the server (1 for E+, and 1 for linear channels)?
It should, that's the way I set it up originally.
Hi there,
I ran Windows 10 updates on my server this morning that hosts Channels and the EPlus docker but am now getting these errors after updating. I tried raising some memory limits in .wslconfig by 4X their original values but that didn't work. Are there other memory settings somewhere I should raise, or other suggestions
fyi I tried pulling the latest EPlus image but that gave the same error, and I also updated to the latest Java. Thanks in advance for any help.
Tim
******UPDATE: I ended up deleting the docker volume folder and re-authenticating all the services and this fixed it. ***********
2025-01-25 10:29:50 > eplustv@4.1.7 start
2025-01-25 10:29:50 > ts-node -r tsconfig-paths/register index.tsx
2025-01-25 10:29:50
2025-01-25 10:30:06 === E+TV v4.1.7 starting ===
2025-01-25 10:30:33
2025-01-25 10:30:33 <--- Last few GCs --->
2025-01-25 10:30:33
2025-01-25 10:30:33 [16:0x7f79e62320b0] 16367 ms: Mark-sweep (reduce) 199.2 (211.3) -> 185.6 (204.1) MB, 271.2 / 0.0 ms (average mu = 0.956, current mu = 0.911) external memory pressure; GC in old space requested
2025-01-25 10:30:33 [16:0x7f79e62320b0] 42321 ms: Mark-sweep 695.1 (713.3) -> 694.5 (700.3) MB, 2130.5 / 0.0 ms (average mu = 0.922, current mu = 0.918) allocation failure; scavenge might not succeed
2025-01-25 10:30:33
2025-01-25 10:30:33
2025-01-25 10:30:33 <--- JS stacktrace --->
2025-01-25 10:30:33
2025-01-25 10:30:33 FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
2025-01-25 10:30:50 npm ERR! path /app
2025-01-25 10:30:50 npm ERR! command failed
2025-01-25 10:30:50 npm ERR! signal SIGABRT
2025-01-25 10:30:50 npm ERR! command sh -c ts-node -r tsconfig-paths/register index.tsx
2025-01-25 10:30:50
2025-01-25 10:30:50 npm ERR! A complete log of this run can be found in: /root/.npm/_logs/2025-01-25T16_29_50_703Z-debug-0.log
Glad you were able to get this figured out @Plasmanut. I'm guessing something weird happened to your config folder and it needed to be reset.
I pushed out a new release tonight. There were some big changes in it, especially to fix a issue with Paramount+ playback. This change effects all providers, but it seems to be pretty solid at this point. But let me know if you get new issues when you try to play a channel.
I also added a new "Options" section in the UI that will allow you to change things like "Start Channel Number", "Number of Channels", "Dedicated Linear Channels", and "Proxy Segments". It'll automatically grab the values from your environment variables and save them to a DB when you first migrate.
i am unable to access the web ui on the new container and it appears like none of the channels work.
i even deleted my app config directory and that also didn't help.
on windows 11 using docker desktop
get this when accessing the web ui:
1 Like
This exactly happened to me too.
Windows 10 Pro 22H2, docker desktop 4.37.1
Yup seems to be an issue: v4.1.8 Webpage won't load · Issue #141 · m0ngr31/EPlusTV · GitHub
Wonder if it's a Windows specific issue... I don't have a machine to test with Windows. Maybe I'll try spinning up a VM and see if I can reproduce that way
3 Likes
Can you post your full logs? Do you see that issue before you try to open the web interface?
It populates in the logs as soon as you enter the xxxxx:8000 address and hit enter.
I just pushed up 4.1.9. As a blind test to see if it'd fix the issue. Hopefully it works so I don't have to spin up a VM 
1 Like
Will try now and report back...
No dice...
2025-01-28 11:49:08 === E+TV v4.1.9 starting ===
2025-01-28 11:49:09 Refreshing device token (ESPN+)
2025-01-28 11:49:09 Refreshing device refresh token (ESPN+)
2025-01-28 11:49:09 Refreshing BAM access token (ESPN+)
2025-01-28 11:49:14 Server started on port 8000
2025-01-28 11:49:14 === Getting events ===
2025-01-28 11:49:14 Looking for ESPN+ events...
2025-01-28 11:49:14 Looking for ESPN events
2025-01-28 11:49:19 Looking for FOX Sports events...
2025-01-28 11:49:19 Looking for MLB.tv events...
2025-01-28 11:49:20 Looking for B1G+ events...
2025-01-28 11:49:21 Looking for NFL events...
2025-01-28 11:49:21 Looking for CBS Sports events...
2025-01-28 11:49:21 === Done getting events ===
2025-01-28 11:49:21 === Building the schedule ===
2025-01-28 11:49:21 === Done building the schedule ===
2025-01-28 11:49:31 TypeError: Cannot read properties of null (reading 'callbacks')
2025-01-28 11:49:31 at stringBufferToString (/app/node_modules/hono/dist/cjs/utils/html.js:53:27)
2025-01-28 11:49:31 at async stringBufferToString (/app/node_modules/hono/dist/cjs/utils/html.js:56:9)
2025-01-28 11:49:31 at async Promise.all (index 1)
2025-01-28 11:49:31 at async stringBufferToString (/app/node_modules/hono/dist/cjs/utils/html.js:44:26)
2025-01-28 11:49:31 at async resolveCallback (/app/node_modules/hono/dist/cjs/utils/html.js:120:13)
2025-01-28 11:49:31 at async responseViaResponseObject (/app/node_modules/@hono/node-server/dist/index.js:378:13)