Since I run docker containers on a mini PC with Ubuntu Server, I decided for the heck of it I'd try the docker container version of CC4C and holy cow I wish I would have done this sooner! Now granted, I'm only using CC4C for Weatherscan and then various live web cams, but for these particular things, the docker container version of CC4C loads waaaaaay quicker and flawlessly all the time compared to the node setup I had been using through Windows. Thank you so much @tmm1 !!!!
Is there a way to convert custom main.js back into a docker ?
I'm not certain that NESN is DRM'ed. I posted about this in the ESPN+ & FOX Sports with Custom Channels via EPlusTV - #2635 by DaveTheNerd thread, and @tonywagner indicated there might be a way to test for that. Happy to do that testing, I just don't know how to confirm it (but I'm fairly nerdy and happy to learn! LOL).
If you have the m3u8 for the channel, I have some scripts that can see if it is DRM protected.
I just PM'ed you.
UPDATE:
I figured out how to use 142.x+ Chrome (or whatever build you want from the chrome testing builds)
Step 1)Install Chrome 142.x using this script
npx @puppeteer/browsers install chrome@142
or
npx @puppeteer/browsers install chrome@stable
This will give you the latest testing build <139 are not supported any longer.
Step 2)Uninstall Chrome & Delete folders & Copy the folder with chrome to
C:\Program Files (x86)\Google\Chrome\Application
&
C:\Program Files\Google\Chrome\Application
or the appropriate folder for your mac.
Step 3)Run Chrome capture. I just released a new one ncc-08-0.js on github
This will have to work until Google patches the issue.
All testing builds will have this banner and you cant remove it afaik
1 Like
Thanks for doing this! I've never used your unified stream EPG. Do we have to do this in order to make Chrome Capture work with 142.x+? Apologies for the confusion.
Edit: Never mind. I found Unified Stream for EPG + M3U - Chrome Capture + HDMI Capture Compatiblee and now I am understanding. 
Thanks!
I have custom main.js that needs more refining but any node main.js or docker should work but going to increase support for other sites
For Proxmox users, I've updated the instructions for creating an LXC version of cc4c. This works with the latest stable Chrome (140.0.7339.80 as of this writing), Node v22.19.0, and uses the most recent code base (2.0.1) from the fancybits/chrome-capture-for-channels repo:
Apologies for the ignorance, but:
- Can this work with a custom main.js
- Is it more efficient than a docker / other method
- Can you make a video of you installing it for those less intelligent.
Sounds like you're not a Proxmox user:
Yes.
Yes to Docker.
That's what the step-by-step linked above is for -- but it's targeted at existing Proxmox users.
Would it be possible to have a 1 click installer? Regardless, I will attempt to do as stated on the guide sometime soon. I apologize for frustrating you, has anyone else been able to install it as per the guide?
Project One-Click is strictly for Docker projects utilizing Portainer.
Do you already have a system running Proxmox? If not, that's the bigger project -- adding a cc4c LXC is trivial in comparison.
No frustration on my end, though focusing on quality of posts rather than quantity helps to keep the content on the forum the most useful for everyone.
Multiple people have used the LXC guide successfully in the past, but I'm sure I'm the only one who's used the updated version I posted a few hours ago.
One of the beauties of virtualization though (like Proxmox), is that it's easy to spin-up a new container to test a step-by-step, after all the steps are determined -- and I did that before posting the update.
Wow guys so many random ways sports are on now I need to do YouTube too apparently YouTube has live sports as well chargers game so paolo
It keeps updating to 139 on Mac. Any other things I should be doing? For the first command, I used sudo rm -rf.
Windows or Mac?
Mac
I've given up on this source unless someone can show that there's a stable Windows release that doesn't get hosed by updates. Have disabled Google updates in the past and still been burned when Chrome updates somehow, just tired of dealing with it.
You're always chasing your tail with this source.
@GTFan This release . Go to services.msc and disable/stop Google Update services (2 entries). Go to program files(x86), Google / Update and rename the update exe. That will be stable 138. You can use test chrome but peacock bans it.
1 Like
I am running the docker version which I run through an Ubuntu Server 24.04.3
After first installing the container, everything runs fine. But I have scheduled daily reboots of my Ubuntu Server and everytime after it reboots, my cc4c container will not work. I've tried stopping it and restarting it and no matter what it won't work. But, if I remove the container and reinstall it, then everything is back to normal...until of course after the next reboot. I'm hoping someone can help me fix this problem. I tried ChatGPT and did a few things it suggested, but still no luck. Here are the error messages that I'm getting:
(EE)
Fatal server error:
(EE) Server is already active for display 99
If this server is no longer running, remove /tmp/.X99-lock
and start again.
(EE)
07/09/2025 18:27:30 *** XOpenDisplay failed (:99)
*** x11vnc was unable to open the X DISPLAY: ":99", it cannot continue.
*** There may be "Xlib:" error messages above with details about the failure.
Some tips and guidelines:
** An X server (the one you wish to view) must be running before x11vnc is
started: x11vnc does not start the X server. (however, see the -create
option if that is what you really want).
** You must use -display <disp>, -OR- set and export your $DISPLAY
environment variable to refer to the display of the desired X server.
- Usually the display is simply ":0" (in fact x11vnc uses this if you forget
to specify it), but in some multi-user situations it could be ":1", ":2",
or even ":137". Ask your administrator or a guru if you are having
difficulty determining what your X DISPLAY is.
** Next, you need to have sufficient permissions (Xauthority)
to connect to the X DISPLAY. Here are some Tips:
- Often, you just need to run x11vnc as the user logged into the X session.
So make sure to be that user when you type x11vnc.
- Being root is usually not enough because the incorrect MIT-MAGIC-COOKIE
file may be accessed. The cookie file contains the secret key that
allows x11vnc to connect to the desired X DISPLAY.
- You can explicitly indicate which MIT-MAGIC-COOKIE file should be used
by the -auth option, e.g.:
x11vnc -auth /home/someuser/.Xauthority -display :0
x11vnc -auth /tmp/.gdmzndVlR -display :0
you must have read permission for the auth file.
See also '-auth guess' and '-findauth' discussed below.
** If NO ONE is logged into an X session yet, but there is a greeter login
program like "gdm", "kdm", "xdm", or "dtlogin" running, you will need
to find and use the raw display manager MIT-MAGIC-COOKIE file.
Some examples for various display managers:
gdm: -auth /var/gdm/:0.Xauth
-auth /var/lib/gdm/:0.Xauth
kdm: -auth /var/lib/kdm/A:0-crWk72
-auth /var/run/xauth/A:0-crWk72
xdm: -auth /var/lib/xdm/authdir/authfiles/A:0-XQvaJk
dtlogin: -auth /var/dt/A:0-UgaaXa
Sometimes the command "ps wwwwaux | grep auth" can reveal the file location.
Starting with x11vnc 0.9.9 you can have it try to guess by using:
-auth guess
(see also the x11vnc -findauth option.)
Only root will have read permission for the file, and so x11vnc must be run
as root (or copy it). The random characters in the filenames will of course
change and the directory the cookie file resides in is system dependent.
See also: http://www.karlrunge.com/x11vnc/faq.html