@bnhf
I am doing a fresh install of Channels onto a Synology and also installed OliveTin via Portainer. All good that far, but when I try to use OliveTin to one-click install CC4C, I'm getting invalid argument, doesn't match int even when I stick with the default values. Any tips on which variable might be causing it?
Thanks!
It's the CDVR_START_CHAN field. I have it set to only accept an integer, but you need to leave it as # to use existing M3U numbering. I'll fix that, and push a new version, but in the meantime put a starting channel number in that field and it should work.
Done. Pushed as bnhf/olivetin:latest (aka bnhf/olivetin:2025.06.19). Using the default # value in the CDVR_START_CHAN field should now work as expected.
@bnhf
Thanks for such a quick fix. That got me past the error, now I am hitting a Portainer error where it doesn't think olivetin has a valid authorization token. There is an API Key env variable so not sure where I went wrong there.
What method did you use for the initial OliveTin install?
You can always delete the existing Portainer Access Token, and create a new one. Copy and paste it to a safe place, then stop the OliveTin stack and replace whatever value you have now for PORTAINER_TOKEN with this new one.
@bnhf
I added it to an existing Portainer instance using your instructions in this thread:
Since you mentioned PORTAINER_TOKEN it looks like that has no value in my olivetin stack. Probably why I'm getting the error! I'll try generating one in Portainer and putting it there.
@bnhf
Adding a key to PORTAINTER_TOKEN got me there. Thanks again.
Now to figure out if I can find the right stream URL for NBC Sports Bay Area, but that's a whole other problem...I appreciate the tech support!
Do i.have to edit the default input parameters to.get a site to stream in fullscreen?
Just dropping this here as I'm at work till late
My CC4C won't load any channels I only use it for NBC.... I run it on my dedicated Channels PC as a straight windows environment I rechecked all and all seem to look ok i also updated it to latest release BUT now the Chrome window does not open for me to choose my login info
I used to see the chrome window when I'd remote in to that pc as it's headless.
I'll digg deeper when I find time BUT figured someone may have had this already
Hi how are you? I am having the same problem, did you find a fix by any chance? Thanks in advance!
Hello @dravenst when I try to open any channel using your CC4C fork or your CH4C fork the chrome window wont open at all. I have verified that all is correct multiple times and even reformatted my minipc but I am still having the same problem, could you please help me? Thanks in advance and sorry for the bother.
same issue here
FIXED IT !!!!
Uninstall current Chrome..... Install Chrome Version 135.0.7049.96 DISABLE all Chrome updaters I needed to actual change the .exe to .exe1 inside the various chrome install locations and "services" applet Do all this while offline (had to unplug my modem from the router since my Channels PC is headless) I'm running the Orig CC4C Win exe via Power-shell auto-start I was able to login to NBC on remote pc when Chrome opened and was finally viewable.
Hello thanks for the help, quick question, is it 100 percent necessary to change the exe to exe1 because i have done everything the way you suggested but unfortunately it doesn't work. Sorry for the bother and thanks in advance!
I disabled both "updaters" in this location C:\Program Files (x86)\Google (look in folders etc)
Also disabled all google update services in "services" applet
After all the above Chrome finally stopped updating and is "stuck" at ver 135 and survives a reboot
my chrome browser also updated and now won't open. I uninstalled the app and reinstalled version 135 and all it does is close immediately upon opening. I tried even older versions and they also crash immediately until I get to versions like 123 and it stays open. However, when I open YouTube TV web it tells me to update my browser with an error trying to play LiveTV
I fixed my issue. I had to uninstall Chrome, then delete my Chrome cache folder, then reinstall Chrome v135, then delete my CC4C folder, then reinstall CC4C (Node advanced method) and then replace my saved main.js file and log in to YouTube and NBC again.
I didn't need to delete my CC4C folder I just force stopped it from task manager It was the Chrome auto updating that was annoying BUT glad its back and running
I think somehow my cache profile for Chrome was not compatible with the older version 135 or even any version 130 or newer. The Chrome browser would simply not open at all with CC4C until I removed the entire cache folder from Chrome.
Sometimes a bit of maintenance on that front goes a long way. I use Bleachbit for stuff like that. Sometimes the cache/cookies messes things up with these things