OScam Error Codes Explained

When working with OScam, understanding error codes and status messages is essential for diagnosing and resolving issues quickly. OScam provides detailed logging that can help pinpoint exactly what is going wrong with your configuration, readers, or network connections. This guide covers the most common error codes and status indicators you will encounter, along with practical troubleshooting steps for each one. All error messages can be viewed through the OScam web interface log section or in the system log file.

Reader Status Indicators

The OScam web interface uses color-coded indicators to show the status of each reader. Understanding these indicators is the first step in troubleshooting. A green indicator means the reader is online and functioning correctly. Yellow indicates that the reader is connected but has not yet processed any ECM requests, which is normal if no encrypted channel is currently tuned. Red means the reader is offline or experiencing a connection error.

A gray indicator means the reader is disabled in the configuration. If you see a reader stuck in a connecting state (often shown with a rotating or flashing indicator), it typically means OScam is attempting to establish a connection but is being blocked, either by incorrect credentials, network issues, or server-side restrictions.

Connection and Authentication Errors

Connection refused: This error appears when OScam cannot establish a TCP connection to the remote server. The most common causes are an incorrect server address or port number in your reader configuration, the remote server being offline, or a firewall blocking the connection. Verify that the device field in your reader block contains the correct hostname and port, and test network connectivity to the server using ping or telnet.

Connection timeout: Similar to connection refused, but this indicates that OScam waited for a response from the server and did not receive one within the configured timeout period. This is often caused by network routing issues, high server load, or restrictive firewalls that silently drop packets rather than rejecting them. Check your internet connection stability and try increasing the reconnecttimeout value in the reader configuration.

Authentication failed / Login failed: This error means OScam successfully connected to the server but the credentials were rejected. Double-check the username and password in the account field of your reader block. Ensure there are no extra spaces or special characters that might have been introduced during copy-pasting. Note that credentials are case-sensitive. If credentials were recently changed by your provider, update them in the oscam.server file and restart OScam.

ECM Processing Errors

ECM rejected / not found (0x00): The server received the ECM request but could not decode it. This usually means the server does not have the right subscription or smartcard for the requested channel. Verify with your provider that your subscription covers the channel you are trying to watch. It can also occur if the CAID or provider ID filtering in the reader configuration is too restrictive.

ECM timeout: The reader received the ECM request but did not return a control word within the expected time. This results in a frozen or black screen. Common causes include slow server response times, network latency, or an overloaded server. If you have multiple readers, ensure the loadbalancer is enabled so that slow readers are automatically deprioritized. You can also adjust the ecm_timeout value in oscam.conf, though setting it too high can cause noticeable channel switching delays.

No matching reader: OScam could not find any reader capable of handling the ECM request. This means none of your configured readers support the CAID or service ID of the channel you are trying to watch. Check that your readers are assigned to the correct groups and that the user account in oscam.user has access to those groups. Also verify that no CAID filters are accidentally excluding the needed encryption system.

Protocol-Specific Errors

CCcam handshake failed: This error occurs during the initial connection setup with a CCcam server. It can indicate a protocol version mismatch, corrupted network packets, or an issue with the server's CCcam implementation. Try adjusting the cccversion parameter in your reader block to match the server's expected version. Common values include 2.0.11, 2.1.1, and 2.3.0.

Newcamd connection lost: The Newcamd connection was established but was unexpectedly dropped. This can be caused by network instability, server restarts, or idle timeout settings on the server side. Ensure your inactivitytimeout is set to a reasonable value and that your network connection is stable. OScam will automatically attempt to reconnect based on the reconnecttimeout setting.

Configuration and System Errors

Config file not found: OScam cannot locate one or more of its configuration files. Ensure that oscam.conf, oscam.server, and oscam.user are all present in the correct configuration directory. On Enigma2 receivers, this is typically /etc/tuxbox/config/. Check file permissions to ensure OScam has read access.

DVB API error / Device busy: OScam cannot access the DVB hardware because another process is using it. This typically happens when another softcam instance (such as CCcam) is still running. Stop all other softcam processes before starting OScam. On Enigma2 receivers, use the softcam manager to ensure only one softcam is active at a time.

General Troubleshooting Tips

• Always check the OScam log file first — it provides the most detailed information about what went wrong
• Enable debug logging temporarily by setting a higher log level in oscam.conf to capture more detail
• Use the web interface status page to quickly identify which readers are online and which are experiencing issues
• After making configuration changes, restart OScam to ensure the new settings take effect
• Test network connectivity independently to rule out internet or DNS issues
• Compare your configuration against a known working example to identify discrepancies