CCcam troubleshooting - no picture or no connection
ECMs in the log but no picture, or a line that won't connect? Work through the common CCcam and OScam fixes: ports, clock, credentials and softcam.
1. Confirm the line is up
Use our line tester with one of your C: lines. If the test fails, the line is expired or blocked, or your network can’t reach the server. If it passes, the problem is on the receiver.
2. Check the C: lines
Compare what’s in your config with the lines in your welcome email or portal, character by character. The two servers use different ports, so a line copied with the wrong port fails even though the host is right. Downloading the ready-made CCcam.cfg or oscam.server from the portal avoids typing mistakes.
3. Check the system clock
If the receiver clock drifts more than about 3 minutes, decoding silently fails. Enable NTP and check:
date # confirm date and time are right4. Verify the ECM is reaching CCcam
tail -f /tmp/CCcam.log
# Expect lines like:
# ECM (CAID 0918:000000) on chid 0000 received from xxxxxxNo ECM lines? The receiver isn’t asking CCcam to decode. Check that CCcam is set as the softcam in your image (Menu → Setup → Softcam → CCcam).
5. Check the ECM time
Open the channel info screen. ECM times above about 1500ms show a slow connection between your receiver and our servers. Check whether your own connection is busy (downloads, other streaming) and tell support the channel and time it happens.
6. Firewall or ISP
A few ISPs block outbound CCcam ports. Run the line tester against your host and port to check whether the server answers from the internet; if it does but your receiver can’t connect, the block is on your side.
Still stuck?
Email support@cccam.io with:
- your username
- the last 50 lines of
/tmp/CCcam.log - which channel(s) don’t decode