The problem atm is the same as what's being reported in the cc4c thread -- which is that Chrome 139 doesn't work with cc4c. Mine works, as I'm on an older version of Chrome and have avoided updating.
I would imagine you can specify a previous version of Chrome (the last 138 should be fine), but I'm not sure how that's done since we're getting Chrome from the Google repo. You might need to download it as a deb file and install it that way.
Awesome, thanks! I shall dabble with a downgrade.
Update:
Downgrading to 138 worked like a charm. Thanks again!
There is a new workaround.
@Ryboflavins I just updated the instructions in Post #1 to incorporate the latest stable version of Chrome and have switched the chrome-capture-for-channels repo to clone back to @fancybits -- as @tmm1 has made numerous changes and updates to it:
Also, for those using this Proxmox implementation of cc4c, here's my recommended approach for starting cc4c at login -- along with an auto restart similar to Docker's restart: unless-stopped:
Add the following to the bottom of /root/.bashrc
nano /root/.bashrc
./cc4c.sh
Then create the following shell script and make it executable:
nano /root/cc4c.sh
#!/bin/bash
# cc4c.sh
# 2025.09.11
cd /opt/chrome-capture-for-channels
pkill -TERM -x Xvfb 2>/dev/null || true
pkill -TERM -x x11vnc 2>/dev/null || true
[[ -f /tmp/.X99-lock ]] && rm /tmp/.X99-lock
while true; do
google-chrome --version
echo "Starting xvfb, x11vnc, and npm..."
# Start Xvfb
Xvfb :99 -screen 0 1920x1080x16 &
XVFB_PID=$!
# Start x11vnc
x11vnc -quiet -nopw -display :99 -forever >x11vnc.log 2>&1 &
X11VNC_PID=$!
sleep 1
grep "The VNC desktop is:" x11vnc.log
echo "The VNC port is: $HOST_VNC_PORT"
sleep 1
# Start your npm app
DISPLAY=:99 bun main.js -v $VIDEO_BITRATE -a $AUDIO_BITRATE -f $FRAMERATE -p $CC4C_PORT -w $VIDEO_WIDTH -h $VIDEO_HEIGHT
NODE_EXIT_CODE=$?
echo "node exited with code $NODE_EXIT_CODE"
# Clean up processes
echo "Killing xvfb ($XVFB_PID) and x11vnc ($X11VNC_PID)..."
kill $XVFB_PID $X11VNC_PID 2>/dev/null
wait $XVFB_PID $X11VNC_PID 2>/dev/null
[[ -f /tmp/.X99-lock ]] && rm /tmp/.X99-lock
echo "Restarting everything in 2 seconds..."
sleep 2
done
chmod +x /root/cc4c.sh
Also, you need to add some additional env var values to /etc/environment. Which when done, should be along these lines:
nano /etc/environment
DISPLAY=:99
CHROME_BIN=/usr/bin/google-chrome
DOCKER=true
LIBGL_ALWAYS_INDIRECT=1
LIBVA_DRIVER_NAME=iHD
PUPPETEER_SKIP_CHROMIUM_DOWNLOAD=true
HOST_PORT=5589
CC4C_PORT=5589
HOST_VNC_PORT=5900
VIDEO_BITRATE=9500000
AUDIO_BITRATE=256000
FRAMERATE=60
VIDEO_WIDTH=1920
VIDEO_HEIGHT=1080
VIDEO_CODEC=h264_vaapi
AUDIO_CODEC=aac
TZ=US/Mountain
Finally, logout and log back in for this all to take effect:
exit
When you log back in cc4c will start automatically, with error recovery.
Thanks so much! I setup a fresh container this way and it worked immediately!
Now if only I could get device passthrough to work for hardware encoding.
Intel GPU?
Yup! i7-11700. It works on my Channels LXC, but for some reason Device Passthrough is greyed out now on my containers.
I improved the cc4c.sh script above to be more robust in terms of cleaning up after trapped or untrapped errors. Plus, there are additions to the /etc/environment file that need to be made. Check this post:
Also, for anybody that's made the jump to v2.01, and you want to pull the few minor changes that have been made since:
cd /opt/chrome-capture-for-channels
git pull --ff-only
Updated! Thanks for this.
Thanks for the terrifc guide - I have this deployed in a ProxMox Container and it does work but I can't seem to get hardware encoding working, decode does work according to Chrome's GPU page.
For reference I am using a system with an i7-13700H. Encoding works for other containters (channels, scrypted & plex). Am I missing something or is it not possible? There is a lot of dated discussions saying it's not possible yet I see other people saying it works.
AFAIK it is not possible for chrome to use h/w encoding. Many people have tried but it does not work.
Thanks for clearing that up!
since i'm fairly new to LXC containers - since this is headless how can i run a display or chrome on the container to add user credentials
Both this LXC version, and the Docker version of cc4c support VNC, so once you have an active stream -- connect using a VNC client and enter your credentials.
@bnhf directed me to this thread after I tried rolling my own Proxmox LXC using the Dockerfile as a guide. Alas, I get the same result doing it this way as I did with own attempt. Specifically, the browser exits with the following whenever I attempt to start playback by connecting to http://hostname:5589/stream?url=...
root@cc4c2:/opt/chrome-capture-for-channels# Xvfb :99 -screen 0 1920x1080x16 & x11vnc -quiet -nopw -display :99 -forever & bun main.js -v 9500000 -a 256000
[1] 348
[2] 349
Xlib: extension "DPMS" missing on display ":99".
The VNC desktop is: cc4c2:0
PORT=5900
[2025/12/26 23:18:17.592] Selected settings:
[2025/12/26 23:18:17.595] Video Bitrate: 9500000 bps (9.5Mbps)
[2025/12/26 23:18:17.595] Audio Bitrate: 256000 bps (256kbps)
[2025/12/26 23:18:17.595] Minimum Frame Rate: 30 fps
[2025/12/26 23:18:17.595] Port: 5589
[2025/12/26 23:18:17.595] Resolution: 1920x1080
[2025/12/26 23:18:17.601] Chrome Capture server listening on port 5589
[2025/12/26 23:19:01.854] Launching Browser, Opts {
executablePath: '/usr/bin/google-chrome',
pipe: true,
headless: false,
defaultViewport: null,
userDataDir: '/opt/chrome-capture-for-channels/chromedata',
args: [
'--no-first-run',
'--hide-crash-restore-bubble',
'--allow-running-insecure-content',
'--autoplay-policy=no-user-gesture-required',
'--disable-blink-features=AutomationControlled',
'--hide-scrollbars',
'--window-size=1920,1080',
'--disable-notifications',
'--disable-background-networking',
'--disable-background-timer-throttling',
'--disable-background-media-suspend',
'--disable-backgrounding-occluded-windows',
'--auto-accept-this-tab-capture',
'--allowlisted-extension-id=jjndjgheafjngoipoacpjgeicjeomjli',
'--use-gl=angle',
'--use-angle=gl-egl',
root@cc4c2:/opt/chrome-capture-for-channels# bun main.js -v 9500000 -a 256000
[2025/12/26 23:21:11.923] Selected settings:
[2025/12/26 23:21:11.924] Video Bitrate: 9500000 bps (9.5Mbps)
[2025/12/26 23:21:11.924] Audio Bitrate: 256000 bps (256kbps)
[2025/12/26 23:21:11.924] Minimum Frame Rate: 30 fps
[2025/12/26 23:21:11.924] Port: 5589
[2025/12/26 23:21:11.924] Resolution: 1920x1080
[2025/12/26 23:21:11.930] Chrome Capture server listening on port 5589
[2025/12/26 23:21:30.402] Launching Browser, Opts {
executablePath: '/usr/bin/google-chrome',
pipe: true,
headless: false,
defaultViewport: null,
userDataDir: '/opt/chrome-capture-for-channels/chromedata',
args: [
'--no-first-run',
'--hide-crash-restore-bubble',
'--allow-running-insecure-content',
'--autoplay-policy=no-user-gesture-required',
'--disable-blink-features=AutomationControlled',
'--hide-scrollbars',
'--window-size=1920,1080',
'--disable-notifications',
'--disable-background-networking',
'--disable-background-timer-throttling',
'--disable-background-media-suspend',
'--disable-backgrounding-occluded-windows',
'--auto-accept-this-tab-capture',
'--allowlisted-extension-id=jjndjgheafjngoipoacpjgeicjeomjli',
'--use-gl=angle',
'--use-angle=gl-egl',
'--enable-features=VaapiVideoDecoder,VaapiVideoEncoder',
'--ignore-gpu-blocklist',
'--enable-zero-copy',
'--enable-drdc',
'--no-sandbox'
],
ignoreDefaultArgs: [
'--enable-automation',
'--disable-extensions',
'--disable-default-apps',
'--disable-component-update',
'--disable-component-extensions-with-background-pages',
'--enable-blink-features=IdleDetection',
'--mute-audio'
],
enableExtensions: [
'/opt/chrome-capture-for-channels/node_modules/puppeteer-stream/extension'
]
}
[2025/12/26 23:21:30.597] [Info] Restarting following first-run puppeteer-stream extension installation
OK, let's start with the obvious stuff first:
cc4c doesn't use http:// for its scheme, it's chrome://, as shown in the first post:
None of what you posted here indicates an error, the [Info] message is just to give you a heads-up on why there's a restart of cc4c on the first run of a new installation:
The fact that you're running this command line, suggests you missed the post later on with additional detail on setting up the startup script and additional environment variables. Since that post contains refinements to the restart process, it's important:
Lastly, just to confirm no issues have crept into the process, I created a brand new LXC this morning and ran through the process myself. Here's the console output from a tune to a Sling channel, after the initial run and Sling login process via VNC:
cc4c3 login: root
Password:
Linux cc4c3 6.8.12-14-pve #1 SMP PREEMPT_DYNAMIC PMX 6.8.12-14 (2025-08-26T22:25Z) x86_64
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Sat Dec 27 07:59:25 UTC 2025 on pts/1
Google Chrome 143.0.7499.169
Starting xvfb, x11vnc, and npm...
The VNC desktop is: cc4c3:0
The VNC port is: 5900
[2025/12/27 01:12:43.678] Selected settings:
[2025/12/27 01:12:43.680] Video Bitrate: 9500000 bps (9.5Mbps)
[2025/12/27 01:12:43.680] Audio Bitrate: 256000 bps (256kbps)
[2025/12/27 01:12:43.680] Minimum Frame Rate: 60 fps
[2025/12/27 01:12:43.680] Port: 5589
[2025/12/27 01:12:43.680] Resolution: 1920x1080
[2025/12/27 01:12:43.686] Chrome Capture server listening on port 5589
[2025/12/27 01:20:02.640] Launching Browser, Opts {
executablePath: '/usr/bin/google-chrome',
pipe: true,
headless: false,
defaultViewport: null,
userDataDir: '/opt/chrome-capture-for-channels/chromedata',
args: [
'--no-first-run',
'--hide-crash-restore-bubble',
'--allow-running-insecure-content',
'--autoplay-policy=no-user-gesture-required',
'--disable-blink-features=AutomationControlled',
'--hide-scrollbars',
'--window-size=1920,1080',
'--disable-notifications',
'--disable-background-networking',
'--disable-background-timer-throttling',
'--disable-background-media-suspend',
'--disable-backgrounding-occluded-windows',
'--auto-accept-this-tab-capture',
'--allowlisted-extension-id=jjndjgheafjngoipoacpjgeicjeomjli',
'--use-gl=angle',
'--use-angle=gl-egl',
'--enable-features=VaapiVideoDecoder,VaapiVideoEncoder',
'--ignore-gpu-blocklist',
'--enable-zero-copy',
'--enable-drdc',
'--no-sandbox'
],
ignoreDefaultArgs: [
'--enable-automation',
'--disable-extensions',
'--disable-default-apps',
'--disable-component-update',
'--disable-component-extensions-with-background-pages',
'--enable-blink-features=IdleDetection',
'--mute-audio'
],
enableExtensions: [
'/opt/chrome-capture-for-channels/node_modules/puppeteer-stream/extension'
]
}
[2025/12/27 01:20:02.797] New target page created: about:blank
[2025/12/27 01:20:02.808] Target page changed: chrome-extension://jjndjgheafjngoipoacpjgeicjeomjli/options.html#55200
[2025/12/27 01:20:02.808] New target page created: chrome-extension://jjndjgheafjngoipoacpjgeicjeomjli/background.js
[2025/12/27 01:20:03.812] Need to initialize stream capabilities
[2025/12/27 01:20:03.960] streaming https://watch.sling.com/1/channel/1a3c345b84b149918e0bad8f797df70a/watch
[2025/12/27 01:20:04.098] Target page changed: https://watch.sling.com/1/channel/1a3c345b84b149918e0bad8f797df70a/watch
[2025/12/27 01:20:04.112] URL contains watch.sling.com
[2025/12/27 01:20:05.203] Target page changed: https://watch.sling.com/dashboard/home
[2025/12/27 01:20:05.527] Target page changed: https://watch.sling.com/modal
[2025/12/27 01:20:30.720] Target page changed: https://watch.sling.com/dashboard/home
[2025/12/27 01:20:31.323] New target page created: blob:https://watch.sling.com/2638aa17-62cd-497c-a988-d44e7a824db8
[2025/12/27 01:20:31.422] Browser page closed: blob:https://watch.sling.com/2638aa17-62cd-497c-a988-d44e7a824db8
[2025/12/27 01:20:32.149] Target page changed: https://watch.sling.com/1/asset/69ef64da41ded9d9a9622bb1fcdebb57/watch
[2025/12/27 01:20:32.811] Browser page closed: chrome-extension://jjndjgheafjngoipoacpjgeicjeomjli/background.js
[2025/12/27 01:20:34.309] Set Sling to Full Screen and Volume to max
All is working as expected.
What is the difference between the 'chrome://' and 'http://' schemes? I have always used 'http://' with @tmm1's Docker image without issue, including the latest image for the last several weeks in my production use.
I do this because I normally use other software besides Channels DVR that doesn't understand the 'chrome://' scheme. I only use (and pay for) Channels DVR for evaluation and comparison purposes and to recommend to less tech savvy friends and acquaintances who want something similar to what I run.
I use mpv and sometimes vlc for testing and MythTV for production and development recording. I do that because I have been a MythTV dev for 22+ years and it has features I rely on that Channels DVR doesn't have. If and when MythTV becomes untenable and Channels is still around, I would probably switch to it but that time isn't now.
No, I saw it but chose to go in a different direction. My intent is to start CC4C from the command line for testing. After it is working that way, I will write a proper systemd unit file for it and contribute it back here. That will allow CC4C to be started and stopped like a normal service and not co-opt the SSH login.
[/quote]