Setting up OScam server: complete guide 2026

Currently, OScam is one of the most popular solutions for card sharing. Setting up OScam server may seem like a complicated task, especially if you are dealing with configuration files for the first time. In this article, I will share my experience and show you how to properly set up the OScam server so that your clients can connect without issues and the cards are read successfully. We will cover the main configuration files, settings for readers and clients, as well as common errors. So, if you are looking for working config examples and explanations of parameters, you have come to the right place!

Structure of OScam configuration files

All OScam configuration files are usually located in the directory/usr/local/etc/ or/etc/tuxbox/config on Enigma2 receivers. Each of these files plays its role in configuring OScam.

Location of configs: /usr/local/etc/ and /etc/tuxbox/config

If you installed OScam by default, the configs will be in/usr/local/etc/. On Enigma2 receivers, the path may be different —/etc/tuxbox/config. You can always specify your own path using the flag-c /path/ when starting OScam.

Purpose of oscam.conf, oscam.server, oscam.user, oscam.services

Main configuration files:

• oscam.conf — global settings and protocols.
• oscam.server — description of readers (cards and sources).
• oscam.user — client accounts.
• oscam.services — grouping of caid and providers.

Don't forget to set the correct permissions on the configs, especially on those that contain passwords:chmod 600 for files with passwords.

How OScam finds the config folder (key -c when starting)

When starting OScam, it looks for configuration files in the standard directory unless you specified another path using the flag-c. It is important to remember this to avoid problems with loading configs.

Basic setup of oscam.conf and web interface

Now let's move on to the basic settings of OScam. Let's start with the fileoscam.conf.

Section [global] and logfile

Here is an example of a section[global]:

This section sets the path to OScam logs, which will help you with diagnostics.

Section [webif]: httpport, httpuser, httppwd

To configure the web interface, add the following section:

The web interface is the main diagnostic tool. The Readers, Users, and Status tabs will help you monitor the status of readers and clients.

Enabling protocols: [cccam], [newcamd], [camd35]

To connect protocols, add sections:

Note that forCCcam it is better to setnodeid manually to ensure stability.

Checking startup via the web interface (port 8888)

Start OScam and check access to the web interface athttp://ваш_IP:8888. If everything is configured correctly, you will see the OScam management page.

Configuring readers in oscam.server

Now let's look at how to configure readers.

Local card: protocol, device, caid, detect

Here is an example of a local reader via a smart card reader:

Pay attention to the parametersmhz andcardmhz. They must match for successful card initialization.

Network reader via cccam protocol (reseller line)

Example of a network reader:

Heregroup links the reader to the client, which is important for proper operation.

Newcamd reader: key, port, ident

Example configuration of a newcamd reader:

This reader must also match the group with the clients.

Parameters group, emmcache, ecmwhitelist

Parametergroup connects the reader with the clients. It is important that they match; otherwise, the client will not have access to the card.emmcache andecmwhitelist will help configure the filtering of unnecessary ECM.

Client configuration in oscam.user

Now let's move on to client configuration.

Account: user, pwd, group

Example of client account configuration:

The group must match the reader's group; otherwise, the client will not have access to the stream.

Restrictions: au, caid, ident, chid

You can add restrictions for the client:

Parameterau is responsible for the transmission of EMM updates.

Parameters sleep, uniq, cccmaxhops, cccreshare

Other important parameters:

• sleep — waiting time before reconnecting.
• uniq — prohibits simultaneous connections with the same login.
• cccmaxhops andcccreshare — control of reshare.

Group mismatch is the most common reason for the "client online, but no channels" problem.

Protocols and ports: what to choose

Several protocols are available in OScam, and the choice depends on your case.

CCcam (port 12000 by default) — compatibility and hops

CCcam is the most widely used protocol for sharing. By default, it operates on port12000 and supports reshare and hops features, making it versatile for card sharing.

newcamd (525) — stability and binding to caid

The newcamd protocol operates on port525 and is strictly bound to caid and ident. It provides stability for a single card, but is not as versatile as CCcam.

camd35/cs378x — UDP and TCP options

The camd35 and cs378x protocols are designed for communication between OScam servers. The first uses UDP, while the second uses TCP. The choice depends on your network and requirements.

Port forwarding on the router and firewall

If you want your server to be accessible from the outside, you need to set up port forwarding on the router and open ports in iptables or ufw. Don't forget to check if you have a static IP or use DDNS.

Diagnostics and typical errors

When setting up OScam, various errors may occur, and it is important to know how to diagnose them.

Reader statuses: CARD OK, NEED INIT, DISABLED

Reader statuses can be checked in the web interface. If you seeNEED INIT, it means that the card has not initialized. Check the mhz and cardmhz parameters, as well as the power supply to the card reader.

Log analysis: cat oscam.log and debug levels

To analyze logs, use the commandcat oscam.log. You can set the debug level using the parameter-d ordebuglevel.

ECM errors: 'no matching reader', timeout, 'group'

Typical errors you may encounter:

• no matching reader — check if the group and caid match.
• timeout — network issue or slow card.
• account not found — check the correctness of the user and pwd input.

Connection check: telnet host port

To check port availability, use the commandstelnet host port ornc -zv host port. If the port is closed, set up port forwarding on the router.