Hi,
After the cwpsrv 1.24.0-2 package was installed on 28 July 2026, the cwpsrv
service failed to start on two of my servers, making the panel completely
unreachable (ports 2030/2031/2082/2083 down, "Service Unavailable" on
cpanel.<domain>).
Environment:
- AlmaLinux 8.10 (kernel 4.18.0-553.146.1.el8_10.x86_64)
- cwpsrv-1.24.0-2.x86_64 (installed 2026-07-28 03:42)
- Two independent servers, different hostnames and different domains
Error:
# systemctl status cwpsrv
Active: activating (auto-restart) (Result: exit-code)
Process: ExecStartPre=/usr/local/cwpsrv/bin/cwpsrv -t (code=exited, status=1/FAILURE)
# /usr/local/cwpsrv/bin/cwpsrv -t
cwpsrv: [emerg] cannot load certificate "/etc/pki/tls/certs/hostname.crt":
BIO_new_file() failed (SSL: ... No such file or directory ...)
cwpsrv: configuration file /usr/local/cwpsrv/conf/cwpsrv.conf test failed
On the second server the certificate files issued by AutoSSL were present and
valid:
/etc/pki/tls/certs/hostname.cert (2026-07-21 12:20)
/etc/pki/tls/certs/hostname.bundle (2026-07-21 12:20)
/etc/pki/tls/private/hostname.key (2026-07-21 12:20)
but /usr/local/cwpsrv/conf/cwpsrv.conf was rewritten by the update
(timestamp 2026-07-28 03:42:20) and points to hostname.crt, which does not
exist on the system.
Main issue: no .rpmsave or .rpmnew file was created, so the previous
configuration was overwritten with no backup. It looks like the conf files
are not marked %config(noreplace) in the spec file. Any local customisation
in /usr/local/cwpsrv/conf/ is silently lost on update, and the service then
refuses to start.
Workaround that restored the service:
cat /etc/pki/tls/certs/hostname.cert /etc/pki/tls/certs/hostname.bundle \
> /etc/pki/tls/certs/hostname.crt
chmod 644 /etc/pki/tls/certs/hostname.crt
/usr/local/cwpsrv/bin/cwpsrv -t && systemctl start cwpsrv
Questions:
1. Could the conf files be marked %config(noreplace), or at least backed up
as .rpmsave before being replaced?
2. Is hostname.cert vs hostname.crt an intentional naming change? If so,
could the update create the missing file or a symlink instead of leaving
a broken configuration?
Has anyone else hit this after 1.24.0-2? Thanks.