Hello,
I have encountered an issue with the Apache hostname VirtualHost configuration on both AlmaLinux 9 and AlmaLinux 10.2 installations running CWP.
I'm currently testing CWP 1.30 on AlmaLinux 10.2, where the following Apache VirtualHost configuration files for the server hostname were missing:
/usr/local/apache/conf.d/hostname.conf
/usr/local/apache/conf.d/hostname-ssl.conf
I previously encountered the same issue on AlmaLinux 9.
On AlmaLinux 10.2, I verified that both original CWP templates are present:
/usr/local/cwpsrv/htdocs/resources/conf/web_servers/main/httpd/conf.d/hostname.conf
/usr/local/cwpsrv/htdocs/resources/conf/web_servers/main/httpd/conf.d/hostname-ssl.conf
I also used the Change Hostname feature in CWP to configure the hostname SSL certificate. The certificate was successfully generated and works correctly on the CWP administration panel (port 2031).
However, this operation did not generate the missing Apache VirtualHost configuration files.
As a result, Apache did not have a dedicated SSL VirtualHost for the server hostname, causing the following issues:
- Accessing the server hostname over HTTPS on port 443 presented the SSL certificate of another hosted domain.
- Accessing the /roundcube/ path through the server hostname redirected to /webmail/ instead of opening Roundcube directly.
For comparison, I have two existing AlmaLinux 8 / CWP servers where both hostname VirtualHost configuration files exist and Roundcube works correctly under /roundcube/.
Temporary workaround:
I manually created the missing configuration files:
/usr/local/apache/conf.d/hostname.conf
/usr/local/apache/conf.d/hostname-ssl.conf
The configuration includes the appropriate hostname SSL certificate directives and reverse proxy rules for Roundcube and phpMyAdmin.
After validating the Apache configuration and reloading the service:
- Apache presented the correct hostname SSL certificate on port 443.
- The /roundcube/ path worked correctly and returned HTTP 200.
- HTTPS worked correctly over both IPv4 and IPv6.
The original CWP templates are present, but the corresponding Apache VirtualHost files were not generated automatically.
Since the Change Hostname feature did not resolve the issue either, I suspect there may be a problem with the generation or deployment of these configuration files.
Could you please confirm whether this is a known issue affecting CWP on AlmaLinux 9 and 10, and whether the hostname Apache VirtualHost files are expected to be generated automatically during installation?
Thank you!