primary domain certificate error after update to 1.52.1

[Capino]

Last Friday we updated Directadmin to version 1.52.1.
since that moment we have problems with the default domain certificate.

On the admin page https://www.example.com:2222 there is no problem, but when a user tries to open roundcube or the phpmyadmin page from within the admin there is a certificate error.

The browser gives the message "Your connection is not private" with "NET::ERR_CERT_COMMON_NAME_INVALID"
When I look at the certificate for this page (https://www.example.com/phpmyadmin) there is a certificate from one of the websites directadmin is running.

I already tired to rebuild nginx_apache and rebuild the rewrite_confs.

How can I setup the certificate so the phpmyadmin and roundcube page will use the server certificate again?

 

[Capino]

I have decoded the SSLCertificateFile that is used in /etc/httpd/conf/extra/httpd-vhost.conf, /etc/httpd.conf.httpd-ssl.conf and the ssl_certificate that is used in /etc/nginx/vhost.conf.

All the certificates used there are from the server url.

 

[Capino]

my directadmin.conf has the letsencrypt certificate configured according to https://help.directadmin.com/item.php?id=629
Also /usr/local/directadmin/conf/cacert.pem has the correct ca that corresponds with the hostname.

Weird thing is that i can connect to phpmyadmin and roundcube over http in stead of https.

 

[Capino]

After some testing and editing i found out that the LINKEDIPSSL in /usr/local/directadmin/custombuild/configure/nginx_reverse/conf/nginx-vhosts.conf did not add the internal IP into /etc/nginx/nginx-vhosts.conf.
For now I have manual inserted the internal IP into /usr/local/directadmin/custombuild/custom/nginx_reverse/conf/nginx-vhosts.conf and rebuild the conf files.
This solved the HTTPS rewrite and gave me the right certificate on the hostname.