Mirakurun Troubleshooting – Fixing the Most Common Errors

Tuner Not Detected After Setup

This is the most common issue, especially on lightweight Linux distributions. Here is how to fix it:

• Run ls /dev/dvb/ to check if your DVB tuner is visible to the OS. If nothing appears, the kernel module is not loaded.
• For Raspberry Pi OS and other minimal distros, build and load the DVB kernel module manually.
• For chardev tuners, verify the startup command in tuners.yml is correct and the binary exists at the specified path.
• Check container logs with: docker logs mirakurun

Admin UI Not Accessible at :40772

• Run docker ps and confirm the mirakurun container is in the list with status "Up"
• Check your docker-compose.yml has the port mapping: - "40772:40772"
• If accessing from another machine, check your firewall allows inbound TCP on port 40772
• Try accessing via IP directly instead of hostname

pcscd Conflict Error on Startup

If you see pcscd-related errors in the container logs:

Alternatively, set DISABLE_PCSCD=1 in your docker-compose.yml environment and mount /var/run/pcscd/pcscd.comm from the host.

Channels Not Showing After Setup

• Check if channels.yml exists at /opt/mirakurun/config/channels.yml
• If the file is empty or missing, add channels manually based on your region
• Restart the container after editing channels.yml

Stream Scrambled or Black Screen

If terrestrial channels play fine but satellite channels show a scrambled or black stream, your B-CAS card setup needs attention. Review the pcscd setup guide for the correct configuration steps.

Container Starts But Immediately Exits

Read the last 50 log lines — the error message will tell you exactly what is wrong. Common causes are missing tuner devices, incorrect file paths in config, or permission issues on device files.