Centova Cast Error: Cluster Host Connection Failure, Connection Refused (111)

Updated: 4 November 2026 · Applies to: Centova Cast 3.2 on AlmaLinux and Rocky Linux 8 and 9 and Debian

When you create or start a stream in Centova Cast, you may see:

Cluster host connection failure for Local server: Connection refused (111)

Error 111 means the web interface could not reach Centova Cast's control daemon, cc-control. The daemon listens on TCP port 2198 and does the actual work of creating accounts and starting streams. Either it is not running, or something blocks the connection to it.

1. Check whether cc-control is running

/usr/local/centovacast/centovacast status

This lists each Centova Cast process: cc-web, cc-app, cc-control, cc-ftpd and cc-imaged. If cc-control shows as not running, restart Centova Cast:

systemctl restart centovacast

On older installations without the systemd unit, use /usr/local/centovacast/centovacast restart. To start only the control daemon: /usr/local/centovacast/centovacast start-ccd.

2. Check the host settings

In the Centova Cast admin area, open Management > Hosts and edit the local server. For a normal single-server installation:

• IP address: 127.0.0.1, not the public IP.
• Port: 2198.
• Authentication key: must match the content of /usr/local/centovacast/etc/rpcshadow on that server.

3. Check the firewall

Test the port from the server itself:

ss -ltnp | grep 2198
timeout 3 bash -c '</dev/tcp/127.0.0.1/2198' && echo open || echo "no connection"

If nothing listens on 2198, cc-control is not running (step 1). If it listens but the connection fails, a firewall rule blocks local traffic: allow it on the loopback interface. When the web interface runs on a separate server, open port 2198 only for that server's IP address.

4. If cc-control keeps stopping

Centova Cast checks cc-control every minute from cron and restarts it if it stopped. If it is down for longer than a minute:

• Check that cron runs the check. Centova Cast keeps its cron jobs in /etc/cron.d/centovacast. On AlmaLinux and Rocky Linux: grep centovacast /var/log/cron; on Debian: journalctl -u cron | grep centovacast. You should see a line about once a minute.
• Look at the control daemon's log, /usr/local/centovacast/var/log/control/master.log, and the system log for the reason it stops (critical messages may go to syslog instead). Check dmesg for the out-of-memory killer too.
• A licence problem can stop Centova Cast as well; a restart then may print "License update failed". Reissue the licence in your Centova client area, then restart.
• Fix file permissions if they were changed by hand: /usr/local/centovacast/sbin/fixperms.

For more detail on diagnosing crashes, see Diagnosing cc-control crashes.

5. Ask for help with a report

Centova Cast can create a diagnostic report for support:

/usr/local/centovacast/sbin/generatereport full

It leaves out highly sensitive data such as the crypto key, but still treat the report as confidential. On a Centova Cast dedicated server from Ucartz, send it with your support ticket.

Official documentation: Controlling Centova Cast and Configuring a firewall for Centova Cast.